Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2024-11-01
Troubleshooting: Generated Documents

Troubleshooting: Generated Documents

Workers can’t view generated documents in their worker profiles.

The worker doesn’t have the necessary access to domain security policies that enables them to view generated documents.
Ensure the worker and applicable security group has the appropriate access to the required domain security policies using the steps below.
Security:
Security Activation
 domain in the System functional area.
  1. Access the
    Domain Security Policies for Functional Area
     report.
  2. Ensure the security group that the worker belongs to has access to these domain security policies:
    • Self-Service: View Generated Documents
    • Worker Data: View Generated Documents
    When the document is generated through:
    • An integration, the worker must also have access to the
      Integration Event
       domain.
    • A job application or candidate action, the worker must also have access to these domains:
      • Candidate Data: Attachments
      • Candidate Data: Offer Details
      • Pre-Hire Data: Employment Agreement
    For more information, see Reference: Candidate Attachments on Candidate and Worker Profiles.
    Ensure that the worker has appropriate access to the following domain security policies:
    • Worker Data: Add Worker Document or Worker Data: Edit and Delete Worker Documents
    • Worker Data: View Generated Documents
    • Self-Service: View Generated Documents
    For job application or candidate generated documents, the following domain security policies apply:
    • Candidate Data: Attachments
    • Candidate Data: Offer Details (Offer Attachments)
    • Pre-Hire Data: Employment Agreement (Employment Agreement Attachments)

The generated document on a Review Documents task is missing in a worker’s My Tasks.

The Workday account of the worker specified in the
Run As User
 field of the Review Documents step configuration is inactive or set to wd-support (see Configure Generated Documents for more information on the
Run As User
 field).
Reactivate the inactive worker on the
Edit Workday Account
 task or assign a new worker by:
  1. Accessing the business process definition that contains the
    Review Documents
     step.
  2. Clicking
    Configure Review Document Step
     and specify an effective date.
  3. Clicking
    OK
     to proceed.
  4. Selecting the
    Run As User
     tab and entering a valid user.
If the Workday account of the selected user in the
Run As User
 field of the
Review Documents
 step configuration is inactive, assign a new user:
  1. Navigate to the business process definition that contains the
    Review Documents
     step.
  2. Click
    Configure Review Document Step
     and specify an effective date.
  3. On the
    Configure Review Document Step
     page, click
    OK
     to proceed.
  4. Select the
    Run As User
     tab and enter a valid user.
  5. Click
    OK
    .
If
Run As User
 is set to wd-support:
  1. Click
    Configure Generate Document
     on the
    Generate Document
     step.
  2. Replace wd-support with an administrator account.
The condition rule criteria on the
Review Documents
 step are not met (for documents that aren’t configured for DocuSign or Adobe Sign).
Check that any condition rules on the generated document are configured correctly. To edit or view condition rules:
  1. Select
    Business Process
     >
    Edit Definition
     from the related actions menu of the business process.
  2. On the
    Review Documents
     step, click
    Configure Document Review
     to access the
    Configure Review Document Step
     task.
  3. Check the currently configured rules in the
    Condition
     field.

A user receives the following error when when migrating a BIRT document from a Preview tenant to a Sandbox tenant using Object Transporter OX 2.0: "You cannot edit Document Template with a past effective date."

You can't use Object Transporter OX 2.0 for migration if the effective date of the source document is in the past, and if the target tenant has an identical document.
In the source tenant (in this case, the Preview tenant), you need to change the document's effective date to a date in the future before attempting to migrate the document again using Object Transporter OX 2.0.
Example: You want to migrate a document from a Preview tenant to a Sandbox tenant. The Sandbox tenant (the target tenant) contains an identical document. The effective date of this document in the Preview tenant (the source tenant) is 4 months in the past, so you update it to today's date or a future date to prevent a migration error.