Best Practices

When you’re configuring your DaVinci flows, you can set a timeout value for the flow as a whole. Because the user’s account could be updated later by anyone with access to the device, a flow with a very long or indefinite timeout could be a security risk. Set a value that minimizes that risk.

The flow timeout begins counting as soon as the flow is launched, which includes time spent at the user selection screen at the beginning of the flow. Since the flow might often wait at this screen in between user signons, you should use a timeout value long enough to cover the gap between signon attempts.

Flows with the original name can be updated by PingOne when we publish flow updates. These updates are not applied automatically, but they add a new latest version to each flow.

By cloning the flows before you apply any customization or use them with customers, you prevent any of your changes or customizations from being overwritten accidentally.

If you want to customize the flows in the Verified Frontline Workers flow pack solution, do so carefully.

Clone the flows before making customizations so that:

Test your customizations in a test environment before importing them into your production environment. Because any additional nodes or flows you add are not part of the standard solution, you must test them to make sure that they’re working as you intend.