Workflow FAQs

Any time you make updates to a workflow that is assigned to a web form, you must reactivate the workflow in order for the web form to update to the new workflow. Otherwise, any requests that are submitted will trigger the last published version of the workflow.

Yes, you can click on the workflow stage to move the rejected request to another stage. Also, any subtask in that stage won't be re-triggered as a result of this change.

Yes, this is possible. However, updating the request to the seeded Closed stage status is not a supported solution.

No, this is currently not a supported view selection.

Enterprise customers only can use the request creation API perform client-to-client integrations. This is possible if customer A is authorized to use and has access to the API key for customer B’s tenant.

Requests deleted from the queue are hard-deleted and cannot be recovered. Currently, OneTrust does not have an audit history in the UI to show who deleted a request.

As soon as there are less than 24 hours left on a day (after 12am in local time), the days left should decrease by 1. For example, if a request is created at 11:50pm with 30 days left, the count decreases to 29 when it turns 12:00 am.

Currently, OneTrust doesn’t support customer stage creation through API integration.

Yes, you will need to enable the workflow stage setting Auto-calculate request deadline at this stage on the Unverified stage.

It depends on many factors and ultimately comes down to what makes the most sense for the organization. OneTrust recommends creating a workflow for each request’s internal fulfillment process that should be followed depending on the data subject’s web form input. Typically, this means configuring a workflow for each request type you support and/or any other unique request use-case.

Yes, if the workflow was previously activated. Requests submitted will be assigned to the previous version of the workflow. Changes to the draft workflow will not display until the draft is activated.