Skip to main content

Core Flex Authorization Template

Authorization Templates that will be used to Authorize Assignments with Core Flex policies should have their Authorization steps configured in such a way that best protects against incorrect data and/

Updated over 2 weeks ago

Authorization Templates that will be used to Authorize Assignments with Core Flex policies should have their Authorization steps configured in such a way that best protects against incorrect data and/or user error.

Any step that could potentially have user-inputted data needed for Benefit Set Line Item calculations should have its Required For Process setting set to Services. This forces the user to address any required information and guarantees proper calculation inputs.

Previous steps - Relocation and Policy from Services Step is set as required for process

As an example, we have both the Relocation and Policy tab a required process for Services

The Services step should have its Required For Process setting set to Assignment Package. This blocks the Assignment Package step from showing anything until the point at which it is useful to the user. As a general recommendation, any step between the Services and Assignment Package steps should have this setting. As a general recommendation, we also change the caption of the services step to Benefits.

Service steps is set as required for process for Assignment Package

The Assignment Package Step should have its Required For Process setting can be set to Routing or Final Approval. Both options behave identically. This prevents potentially unwanted emails and incorrect Authorization completion by hiding Final Routing and Final Approval controls until all exceptions have been approved. As a general recommendation, any step between the Assignment Package and Approval steps should have this setting.

Did this answer your question?