Workday® Docs
Workday® Docs
1 | Docs
1.1 | Steps: Set Up Workday Docs
Prerequisites
This task applies only to business processes that Workday Docs supports.
Set Up Security for Drive for all users who do any actions (create, edit, or view) with Docs
templates.
Workday Docs is currently not translated. To make the user interface appear for users who
have a non-English display language, the security administrator must access the Edit
Workday Account task for all of these users and select the Allow Mixed-Language
Transactions option. This setting causes the user interface for Workday Docs (not the entire
Workday user interface) to display in English.
Security: Security Configuration domain in the System functional area.
Context
Workday Docs enables you to automate the generation of documents using Workday data. Docs is
an alternative to the traditional text block method for creating document templates. Workday Docs
supports several types of documents and business processes.
The Docs security domain in the System functional area manages the ability to use Docs templates.
When setting up Docs, add all users who create, edit, or access Docs templates to the Docs and
Drive security domains.
Steps
1. Create security groups for users who will be working with Docs templates (typically
administrators) and users who will be generating documents (usually Recruiters). These
users might or might not be working with business processes.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 1/24
3/15/23, 3:10 PM Workday® Administrator Guide
5. (Optional) Confirm or update the languages that you want to make available as language
instances in Docs templates by viewing the Languages section on the Edit Tenant Setup –
Global task.
See Reference: Edit Tenant Setup - Global.
Drive
Docs
Document Library
Context
This task applies only to business processes that Workday Docs supports.
The publish feature enables you to work on content at a draft level for as long as you need to,
preventing those changes from being incorporated when the associated business process runs. As
soon as you publish the content, the business process uses the latest content. Workday constantly
auto-saves your changes, but those changes aren't effective in the template until you publish.
Docs doesn't support automated conversion of templates based on text blocks into the
Docs template format.
Docs doesn't support reusable content between templates. Example: If the same content is
in two templates, you need to update it in both.
If you want to automatically share a Docs template with a set of users, you can share a
folder in Drive with individual users or with a security group, and place the new template into
that folder.
Docs doesn't support automatically publishing on a future date. If you want to hold your
changes back until a specified date, you need to manually publish on that date.
Docs doesn't support concurrent editing or publishing of templates by more than 1 user.
Docs doesn't support right-to-left (RTL) language formatting.
When you create a new template, the new template will be available to configure to the
business process even if you haven't published it yet. Until you publish it, the document
generated from it will be blank. We recommend not configuring a template to a BP until after
you publish it.
If you upload a previously downloaded template file, make sure you publish it before
configuring it to the business process.
Steps
1. From Drive, select Add New > Document Template and name the template.
For DocuSign, you must use a name that is fewer than 100 characters. For Adobe Sign,
names can't contain special characters such as the ampersand (&).
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 2/24
3/15/23, 3:10 PM Workday® Administrator Guide
Where applicable, Workday Docs automatically sets the Resulting Document Expiration
Offset to 10 years; currently this value isn't editable.
2. Select a source.
3. Select a category.
You can use segment-based security groups to restrict the document categories displayed
in the prompt.
4. (Optional) Change the base language of the template by clicking Language > Add Language,
then select the new base language.
When you initially create the template, Workday Docs sets the base language to English; any
new language instances will copy the English content as a starting point for your translated
template.
As soon as you save the change to the base language, any new language instances that you
create from the base language template will copy the new base language content.
Existing template language instances retain the same content.
We recommend doing any base language change as a separate action in the Languages
dialog from adding new language instances. If you open the Languages dialog, change the
base language, add languages, and then save, the new languages will inherit content from
the previous base language and not the one you just selected.
5. Configure the layout, such as headers and footers, and the content of the template.
The template initially is in an unpublished state.
A Published (green) or Unpublished Changes (orange) indicator displays at the top of the
template to indicate the status of the content. It doesn't identify individual changes, but the
overall status of the template.
6. (Optional) Add language instances for the template by clicking Language > Add Language.
When you create a language instance, Docs copies the existing content from the base
language into the new instance. Then you use that content as a guide and manually replace
it with the content in the desired language.
You create and manage translated content in headers and footers in the same way as the
template content. Each language has separate headers and footers.
Language instances don't have any specific language requirements; the language name is
simply an identifier that helps you track the different language instances in the template.
If a generated document is sent to a user whose preferred language doesn't match any of
the defined language instances, Workday sends that user the base language document.
7. Click Publish to make the current content active in the template.
As soon as you publish the template, business processes start using the updated template
when generating documents.
When you click Publish, if any errors exist in the template:
A red dot displays next to a language in the text editor drop-down list and the
headers/footers drop-down list if the language instance contains one or more errors
in data fields, condition rules, or images.
A red border displays around the text editor drop-down list and the headers/footers
drop-down list if any language has an error. The red border displays until you fix all
errors in all the language instances.
A red banner and check box display in the condition rule or data field panel, enabling
you to display only the rules or fields with errors.
8. Make additional changes to the template as needed. As soon as you make a change, its
state changes to Unpublished, and the orange Unpublished Changes indicator displays at
the top of the template. Your template changes aren't used in the business process until you
click Publish to activate those changes.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 3/24
3/15/23, 3:10 PM Workday® Administrator Guide
This task applies only to business processes that Workday Docs supports.
Make sure the DWXF file type is a supported type in the destination tenant, by either supporting all
file types or adding it as a supported type. You can find the full instructions in the Drive Admin
Guide here (step 2) .
Make sure that both the source and destination tenants have the same security configuration, and
the same languages defined in the Edit Tenant Setup – Global task.
Context
You can move (migrate) your templates between tenants by downloading (exporting) from a source
tenant and uploading (importing) to a destination tenant. Workday Docs doesn't support OX-based
migration of templates between tenants.
After moving a template between tenants, you must open the template on the destination tenant
before using it in the Configure Generate Document step. Opening the template causes Docs to run
an error check process, confirming that all condition rules and data fields are correctly configured in
the template.
Workday Docs doesn't support replacing existing templates in a tenant. Example: If you have a
template in a Production tenant and you update a template in a Sandbox tenant, you can't replace
the Production template with the Sandbox template. You need to either manually redo the changes
in the Production level template, or upload the edited template as a new template and configure it to
the BP.
Steps
1. Manually migrate all data fields and condition rules used in the template from the source
tenant to the destination tenant. You can use the View Document Template Details report
for this purpose. Your migration might include manually editing Reference IDs or using
Object Transporter. Your goal is to make sure the applicable data fields and condition rules
exist on the destination tenant and that their Reference IDs match between the 2 tenants.
2. With the template open in the source tenant, go to File > Download As > Docs Template. The
template downloads as a DWXF file. You need to be the owner or have Can Edit permission
to do this step. Note that sharing permissions aren't saved in the downloaded template file.
3. From Drive in the destination tenant, select Add New > Upload and upload the DWXF file.
4. Open the template. Reselect the document category.
a. An automatic data migration begins. The migration makes sure all of your data fields
and condition rules map to the template correctly in your destination tenant. You
must do this step before generating; otherwise, errors might occur during
generation.
b. If errors occurred during the migration, an error page displays. Fix any errors by
either migrating any necessary data fields and condition rules or by editing the
Reference IDs so they match.
c. If you fixed errors, refresh the page. You don't need to upload the template again.
When the migration completes successfully, you no longer see the error page and
you can make edits to your template as needed.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 4/24
3/15/23, 3:10 PM Workday® Administrator Guide
From Workday in a Google Chrome web browser, select the Drive option in the Workday main menu
(the avatar/profile drop-down menu).
With Workday Docs, you can create a new document template from Drive and then:
When you are configuring a generate document step in a business process, you can select a Docs
template as the source.
The overall review process (launched from the Inbox) and the business process steps remain the
same.
Docs templates that you create and manage with Workday Docs exist in parallel with traditional
document templates that you create using text blocks (BIRT). When working with your business
processes, you can select either type of template in your BP steps. In many cases, it's desirable to
use Workday Docs to create templates because of its improved usability; however, your template
might have special requirements that Workday Docs doesn't currently support. In these situations,
you can use the traditional document template.
When implementing business processes in Workday Docs, consider that Docs doesn't support:
Reusable content between templates. Example: If the same content is in two templates, you
need to update it in both.
Custom fonts. The template editor, preview PDFs, and generated PDFs currently use the
Roboto font. You can't change this selection.
Automated conversion of templates based on text blocks into the Docs template format.
OX-based migration of templates between tenants. To move templates, you download them
from the source tenant and upload them to the destination tenant, and edit reference IDs if
needed.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 5/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs automatically copies the content of the base language into the new language instance, then
you can customize the new instance for that language.
You can define the languages that are available to add in the Languages section on the Edit Tenant
Setup – Global task. Note that Docs doesn't support right-to-left (RTL) languge formatting.
From the Add Language dialog you can also change the base language of a template. After you
change the base language, any new language instance that you create will copy the new base
language content; existing template language instances retain the same content.
You customize each language instance by replacing the original content with translated content. If
you want styling, layouts, data fields, or condition rules to apply across all language instances, you
need to set those up in the base language before creating the language instances.
To delete a language instance, select it in the Languages dialog and click the X icon. You can't
delete a language if it's assigned as the base; select another language as the base first.
When you publish a Docs template, all of the language instances are published too.
If you don’t add an instance for a document recipient’s language in the Docs template, the
generated document will be sent using the base language.
The way you manage languages for generated documents that are based on Docs templates in
Drive remains the same as for traditional text block based documents:
If you don't specify a language, Workday generates the document using the preferred
language of the Run As User.
If the Run As User doesn't have a preferred language defined in Workday, Workday generates
the document using the language associated with the default locale of the tenant.
If nobody translated the template into a specified language, Workday generates the
document using the base language of the template.
Data field and condition rule formatting in generated documents will continue to be based on the
recipient user's location, not the language instance of the template.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 6/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs Drive BP
Action DomainDomainPermissions
Notes
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 7/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs Drive BP
Action DomainDomainPermissions
Notes
X
Configure Generate Document
Step
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 8/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs Drive BP
Action DomainDomainPermissions
Notes
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 9/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs Drive BP
Action DomainDomainPermissions
Notes
X
Set up the Review Documents
steps
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 10/24
3/15/23, 3:10 PM Workday® Administrator Guide
Docs Drive BP
Action DomainDomainPermissions
Notes
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 11/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Create a Docs
template
1. From Drive, select Add New > Document template.
2. Select a source.
Notes:
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 12/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Docs templates that you create in Drive are owned by the specific
users who created them. Owners can do actions on templates that
other users can't do; for details, See Reference: Docs Template
Actions Available Based on Permissions.
For DocuSign, you must use a name that is fewer than 100
characters. For Adobe Sign, names can't contain special characters
such as the ampersand (&).
You can include optional text that reviewers can add or delete when
generating a document. We recommend that you highlight this text
or format it in a different color to draw the user's attention when
generating the document. The user can make any necessary edits
within the Generate Document step before sending the business
process on.
Copy a From Drive, select the Docs template and click Make a Copy.
template
Share a Docs Share with many users at once by giving them a link, which you generate in
template with the Share dialog.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 13/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
unspecified
users, using a
link (URL)
1. Select a Docs template in Drive and click Share.
2. Enable the Link Sharing option if it isn't already enabled. The ability
to use link sharing is a system setting. If you don't see the option,
check with your administrator.
4. Click Copy Link. Give this URL to people you want to share the Docs
template with.
For more information about sharing, see the Drive User Guide.
Share a Docs Sharing with individual users enables you to set a specific permission level
template with for the person; these settings remain active if you turn off link sharing.
specific users
2. In the Share with Individuals area, type the names of the users that
you want to share with and select a permission level in the drop-
down menu.
3. (Optional) Type a message for the users you're sharing with. The
message displays in the Workday notification that the users receive
after you click Share.
When you share a Docs template with an individual user, the user receives
a Workday notification and (if enabled on the tenant) an email. The user
receives the notification whether or not they have access to the Drive
domain, but they must have Drive domain and Docs domain access to
open the template. For more information about sharing, see the Drive User
Guide.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 14/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Share a Docs Sharing with a group of users enables you to set a specific permission level
template with for the group; these settings remain active if you turn off link sharing. The
security groups ability to use group sharing is a system setting for each Drive item type. If
you don't see the option, check with your administrator to ensure that it's
enabled.
2. In the Share with Groups area, type the names of the groups that
you want to share with and select a permission level in the drop-
down menu.
Preserve a Copy the Docs template or download it in the DWXF file format if you want
previous to preserve the current version of data or content, before updating it.
version of the
Docs template
Remove a From Drive, select the Docs template and click Remove. Drive moves the
Docs template file to the trash.
Recover a From Drive, select Trash. Select the Docs template and then click Restore.
Docs template Workday places restored file in the All Files view.
from the trash
If you select to remove a Docs template that was shared with you but
you're not the owner, you remove your access to the template. The Docs
template disappears from the Drive file list and it doesn't display in the
trash.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 15/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 16/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Add text
If you copy and paste from a text block to a Docs template, Workday
doesn't preserve condition rules and data fields in the Docs template.
The Docs template editor and the PDF previewer use the Roboto font; the
font selection isn't editable.
The size limit for body content, including images, in the Docs template and
the generated document is 30MB. If you try to insert content that causes
the limit to be exceeded, an error message displays and Workday doesn't
save the change.
Manage Click Layout > Headers & Footers to open the header and footer text editor.
headers and
To delete a header or footer, click the actions menu next to the header or
footers
footer and then click Delete. Docs doesn't support reordering headers and
footers, so you need to delete and re-add them if you want to change the
order.
Notes:
If you add more than 1 header or footer, you must add a condition
rule to each header and footer.
When generated, the first header and footer with a true condition
rule displays. The user who has access to the document generation
task can edit and delete headers and footers if there are multiple
headers/footers with a true condition rule.
Header and footer settings apply to all pages; you can't control
individual header and footer values per page.
Defaults:
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 17/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Maximum values:
Header Height (header + top margin): 234 pixels (or 2.44 inches)
Minimum values:
Manage data To insert a data field, click Insert > Data Field. Highlight text, or place your
fields cursor in the document, and click the + icon next to the data field.
To view all data fields added to the document, open the Manage Data
Fields panel.
To delete an individual data field, right-click the field in the editor and select
Delete.
To delete all instances of a data field, click the actions menu next to the
data field in the panel and then click Delete.
To replace all instances of a data field, click the actions menu next to the
data field in the panel and then click Replace All. Find the new field, and
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 18/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
when you click the Add (+) icon, Workday replaces all instances with the
new field.
Workday Docs doesn't support converting data fields; you need to redefine
them in your Docs template.
To create a new data field, you can navigate directly from the Insert Data
Field dialog to the Create Data Field task by clicking Create New at the
bottom of the dialog.
Manage To insert a condition rule, click Insert > Condition Rule; start typing a rule
condition rules name to find it.
Click the + icon to add a blank condition rule (with no content), or highlight
text in the document before clicking the + icon next to the condition rule.
You can add a condition rule to all content types, including data fields.
To view all condition rules added to the document, open the Manage
Condition Rules panel. Click the eye indicator to display or hide content
applied to the condition rule.
To delete an individual rule, right-click the field in the editor and select
Delete.
To delete all instances of a rule, click the actions menu next to the data
field in the panel and then click Delete.
To replace all instances of a rule, click the actions menu next to the rule in
the panel and then click Replace All. Find the new rule, and when you click
the Add (+) icon, Workday replaces all instances with the new rule.
To create a new condition rule, you can navigate directly from the Insert
Condition Rule dialog to the Create Condition Rule task by clicking Create
New at the bottom of the dialog.
Manage
To add a language instance, select Language > Add Language.
language
instances To change the base language, select Language > Add Language and select
the base language you want. After you change the base language, any new
language instances that you create will contain the new base language
content; existing template language instances will retain the same content.
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 19/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
Manage tables To add a table, click Add table. A dashed line shows the table placement.
Add a column or row: Click the blue circle near a column or row.
Set a cell color: With the cursor in a cell, click the Background Color
icon and select a color.
Set a border color: With the cursor in a cell, click the Borders icon,
then the Edit icon, and select a color.
Add a border: Select table cells or the entire table and click the
Borders icon. By default, tables don't have borders.
Resize table columns: Hover over the column edge, click the resize
indicator, and drag.
Delete a column or row: Click the blue line near the column or row
and click Delete row or column.
To delete the table: Click the blue circle in the table corner and click Delete
row or column.
About tables and condition rules: Workday Docs doesn't support the ability
to conditionally use different table cells, rows, or columns. We recommend
either wrapping the content within the cell in condition rules, or wrapping
the entire table in a condition rule and creating a separate table for each
condition.
Insert page From the header or footer menu, click the Page Number icon to insert the
numbers page number. If you want to create a running page number and total, you
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 20/24
3/15/23, 3:10 PM Workday® Administrator Guide
Action Notes
can include text along with the page number values. Example:
Add a link
Click the Insert Link icon to add a URL directly into the text. Highlight text
and then click the Insert Link icon to create a hyperlink in the text.
Lock content Highlight text in the document and click Lock Content.
After you lock content, users with access to the document generation step
can't edit it; however, users can still delete text even if it's locked.
Change fonts
The Docs template editor and the PDF previewer use the Roboto font.
Workday Docs doesn't support changing the font; however, you can change
the text style (paragraph style and headlines).
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 21/24
3/15/23, 3:10 PM Workday® Administrator Guide
Can Can
Action View Edit Owner
X X X
View Docs template
X X X
View Docs template in preview mode
X X X
Copy Docs template
X X X
View list of specific users the Docs template is shared
with
X X
Remove (self) from shared Docs template access
X X
Change share permissions
X X
Edit content
X
Rename Docs template
X
Remove to trash and restore from trash
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 22/24
3/15/23, 3:10 PM Workday® Administrator Guide
Workday recommends that you add the Generate Document Action step and Review Documents
step to the supported business processes definition to generate and view documents using
Workday Docs.
Related Information
Concepts
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 23/24
3/15/23, 3:10 PM Workday® Administrator Guide
https://doc.workday.com/internal/api/webapp/print/83327c72-fb8a-4c34-a4ca-f95c2f79af2a 24/24
When configuring language settings in Workday Docs, it is vital to ensure that the base language is correctly set, as this determines the starting point for new language instances . Changing the base language should be performed independently from adding new languages, as this affects how content is inherited by subsequent language instances . Each language instance requires manual content translation for new headers and footers . If a user's preferred language isn't present among the defined languages, Workday defaults to sending documents in the base language . This configuration calls for preemptive planning to avoid generating documents in unintended languages for diverse user bases. The selection and set-up of language instances should align with anticipated user needs for effective communication and document utility .
To migrate Workday Docs templates between tenants, it's important to ensure that the DWXF file type is supported for migration . The process involves downloading the templates from the source tenant and uploading them to the destination tenant; adjustments to reference IDs might be necessary after the transfer . Challenges may include ensuring compatibility between the source and destination environments and confirming that all required dependencies and security settings are appropriately configured in the new tenant. Additionally, any language instances need to be manually customized once migrated, as automatic conversion of templates isn't supported .
Workday Docs allows customization for multiple languages within a single template by assigning a base language, typically English, from which any new language instance is derived . When you create a new language instance, Docs copies the content from the base language template into the new one, allowing manual replacement with the translated content . To manage language instances effectively, you should ensure that any styling, layouts, data fields, or condition rules are configured in the base language template before adding instances . Additionally, if a document is to be sent in a language not defined in the template, Workday defaults to the base language . Language instances are managed by selecting 'Language > Add Language' in the Docs template interface, allowing users to customize the template for different languages .
Template ownership in Workday Docs can be transferred without disrupting current document processes by using the 'Transfer Ownership' feature in Workday Drive . This action allows the new owner to assume control over the template without affecting its current integration with business processes . It is essential to ensure that the new owner has the requisite permissions and access to the relevant domains, such as the Document Library domain, to manage the template effectively . Communication between the involved parties and updating any administrative records helps ensure a seamless transition, maintaining operational continuity. Additionally, ownership transfer doesn't alter existing sharing settings, so the process remains uninterrupted for other users who interact with the template .
Workday Docs has several limitations regarding template sharing and management. Sharing is managed by placing templates in a shared Workday Drive folder which can be accessed by individual users or security groups . However, Workday Docs does not support simultaneous editing of templates by more than one user, limiting collaborative efforts . Additionally, templates that are automatically shared from a folder will not support effective dates or future automatic publishing, requiring manual updates and oversight . Security controls are essential as template creators need access to specific categories and data fields, which are controlled by the Document Library domain .
Given that Workday Docs doesn't support effective dates for templates, best practices suggest creating a copy of the existing template before making updates . Once changes are completed in the new version, replace the original template in the associated business process with the updated copy . This avoids service interruptions or unintended use of outdated templates . It's critical to publish the new template promptly after verification, ensuring business processes utilize the latest content. Regular audits and precise version controls are recommended to keep track of changes and maintain template integrity over time. Additionally, documenting the updates and informing relevant team members are important steps to facilitate seamless transitions between template versions .
Workday Docs uses visual indicators to manage the publishing status and errors in document templates. An unpublished template is indicated by an orange 'Unpublished Changes' status, which turns green once the template is published . Errors in the template are flagged by red indicators next to the language in the text editor drop-down list, and red borders are displayed until all errors are resolved in all language instances . A red banner and checkbox are available to highlight rules or fields with errors within the data field or condition rule panel . These features assist users in identifying and addressing issues before publishing, ensuring that templates are error-free and effectively integrated into associated business processes .
Using segment-based security groups in Workday Docs to restrict document category access provides the advantage of targeted access control, ensuring that only authorized users can view or modify sensitive document templates . This configuration aids in maintaining data confidentiality and operational efficiency, as users are confined to categories relevant to their roles . However, this setup can also present limitations such as increased administrative overhead to manage and update security groups. Furthermore, there might be challenges in adjusting to organizational changes or ensuring all necessary users have timely and correct access . These considerations are crucial for balancing security with functional access to essential business documents. Additionally, restricted access might hinder collaboration if team members located in different segments cannot share templates effectively, potentially requiring additional processes for cross-group document sharing .
The Document Library domain in Workday Docs plays a significant role in controlling access to categories, data fields, and condition rules for document templates . It ensures that template creators can select only those categories they have permission to access, thus safeguarding sensitive or restricted content . Additionally, it determines access to data fields and condition rules used in templates, which are critical for producing documents aligned with business processes and requirements . This structured access helps maintain the integrity and consistency of document templates across the organization, emphasizing the need for appropriate permissions and security settings in template management. Moreover, as templates can be shared through the Document Library domain, security settings in this domain are crucial to facilitate or restrict collaborative document editing and management .
The lack of right-to-left (RTL) language formatting support in Workday Docs means that documents cannot be effectively created or managed in languages like Arabic or Hebrew . This limitation can significantly impact organizations operating in regions where RTL languages are prevalent, necessitating workarounds such as external tools for document generation and representation. The inability to handle RTL languages internally may lead to inefficiencies and potential data inaccuracies if external document generation methods do not integrate seamlessly with Workday Docs . Additionally, organizations may face challenges in maintaining consistency and meeting compliance requirements, particularly if document audits or verifications require specific language presentations .