INX InFlight

We use the Employment Class selection to manage our shutdown workforce in particular. It'd be great to be able to bulk add/remove people to options available in this field.

As a company we have multiple sites and contractors visit different sites regularly. Can we have the ability to not allow a ceased date to be added where a profile has ana roster activity in the future.

We want to keep people active for a certain amount of time after they have ceased. Currently you have to open the profile from the Group Maintenance results to see when their ceased date was. It would be great if ceased date was a column in the table display (that could be sorted/filtered)

Is it possible to 'remove a comment' from multiple days within a Roster rather than individually

In a person's roles tab, can these roles please appear in date order? Particularly useful when personnel move from site to site in the same company.

Currently, updating the ceased date is necessary to clear reporting queues under "Daily Activity Status." However, it's illogical that the report continues to include activities from inactive users. To improve report accuracy, either inactive users should be excluded from the report entirely or an additional filter should be added to specifically include inactive user data if needed.

Background: Currently, all persons who have 'Read' access within any INX module can see the sensitive personal data (in the Person Details tab) for the people they have access for. With greater legislative requirements in relation to the collection, storage and security of personal data (as well as obligations on organisations to be able to report a potential access and/or worse - a breach), organisations need to look at the data being stored. The fields I am referring to are: General: (most are needed, propose that DOB is hidden - only Admins need to see this) Salutation, First Name, Last Name, Lookup Name, Employer, Supervisor, Network Username, Workgroup, Employee ID, Gender, Date of Birth, Mine Health Number Additional Information: (custom fields I thin could be hidden) USI Number (Custom Field - but I think many with InTuition would use it) Work Contact Details: (agree these are needed) Phone, Mobile, Fax, Onsite Contact, Email Emergency Contact Details: (I believe these should all be hidden - unless Admin) Contact Name, Relationship, Home Phone, Mobile, Address, Suburb, State, Post Code Additional Contact Details: (I believe these should all be hidden - unless Admin) Home Phone, Personal Mobile, Home Fax, Offsite Contact, Street Name, Suburb, State, Post Code Request for Change: I am requesting a number of different changes - one or more of these may address, but only for consideration: In the web UI - Hide all Sensitive Data (outside of the General Fields) to non-Administrators; In the web UI - Change the text to only show "xxxxx" where data is recorded for non-Administrators; In adhoc reports - remove the ability to report on 'sensitive fields' (IE modify the existing standard adhoc reports); Separately, I also believe that the data should also be masked in the DB.

Ability to reserve rooms in bulk so they are not allocated in builds. Admins then able to assign the room to a person once the person is known for that future booking.

Restrict visibility of Date of Birth field to a specific security group

The Carriers table currently does not have an active flag. Implementing a flag will ensure that historical carriers can not be added to new or existing flights.