+Process - Integration and Display of Site Entry Requirement Attachments
unplanned - open for votes
G
Grant Towers
Background:
We currently upload a number of sensitive documents (Medical D&A etc.) into our mobilisation process. We are required to validate and then delete the attachment, prior to submitting the workflow into INX (to prevent the attachment going into INX)
Recommend Action:
Introduce into INX Site Entry Requirements Screen (and also then into +Process) the ability to specify if attachments are integrated, and then if so, whether or not the attachment is published within INX to Readers.
This would result in significant time saving if we didn't have to remove attachments for every single mobilisation.
Kassie Conway
Hi Grant,
Thank you for your submission above.
Its my understanding that you would like to have the ability to configure within INX, once a compliance has been provided within a workflow in +Process (When it has been deemed as a site entry requirement via Worker Type), wether or not you would like the provided document to be imported or not upon Commit/Approval.
Would you like the option to have document to be imported - but not visible to a particular security group?
Or not imported at all?
Would it benefit to have this configuration at a Compliance Level for the instances a compliance has been mapped to a ROLE within Intuition? Or Would it be satisfactory to just have the config option at the Site Entry Requirement stage within InFlight?
Looking forward to hearing back from you.
I will leave this post Open to allow for Comments and Votes.
Kind regards
Kassie & The Product Team
Kassie Conway
unplanned - open for votes