New and other Initiatives

Background: Currently, there is no way to bulk modify/delete securities for personnel no longer in the business. Request For Change: We need a way to bulk review (or delete) user access (like has been done within InControl Event User Security) to be able to easily review/modify/delete security items for: InControl: Security Roles Combined (currently have to open each security type manually...) InTuition: User Security InFlight: Camp Security Site Security User Security Even the ability to toggle inactive personnel only, so you can easily add new access for personnel (or delete the access altogether...). Thanks and Regards,

Background: We all need to regularly update organisational structures within INX. We also like to make class values inactive to keep it easy for end users to ascertain the structure and their workgroups. The issue is that a number of versions ago, the decision and change was made to clear/de-select the value of an inactive class value so that it appears as null. The issue with this is as per above. If we need to make structural changes, we have to: Make the class value active again; Change the structure as required; then Deactivate the class value again... Literal waste of time... Also, for those that don't know, you will end up large numbers of workgroups that are not linked to class members - the system doesn't tell you it has removed them... (just says "Workgroup details updated successfully" Proposal: I cannot see any reason that any company would would to default the value to null. If you want null, select null. Change the logic so that if we make changes to the structure (and the selected class value is not changed) stop removing inactive class values - leave them as they are. Note: I agree that as it is, if the class value is inactive, it shouldn't appear in the dropdown.

Background: We have an issue with data entry whereby there are spaces in email addresses – no matter how hard we try… We cannot eliminate them. With other systems (LMS/Assessor) are now using the email address as a unique id (such as login). The issue is that INX core doesn’t validate email address at all and we have ongoing issues with LMS/Assessor when people have duplicate/invalid emails. Recommended Action: There needs to be validation in INX Core – this will ensure that the email address remains updated as required: The Validation needs to include the following validation on emails, but not limited to: • Must be unique; • Must include a “@”; • Must not include any “ “, (both leading and trailing); • Etc…

Some of the naming conventions within INX have specific gender terms, e.g. "Manning Reports" can this be renamed to "Personnel Reports". Another example is "Mandays" can this be referred to as "Exposure hours or day".

Develop internal pipelines to deliver module DUS sheets pre-filled with client fields and field values. Providing this will accelerate the client ability map ahead of the bulk data upload.

Have the ability to translate headings, or non-custom fields, to other languages for countries where English is their second language.

In the Organisation/Employers Admin area we can capture ABN's however we also deal with NZ and other international companies where we wish to capture a unique identifier. It would be great if the ABN field could cater for all options in this regard.