One-Click Actions (OCA’s) are predefined document generation and delivery settings in DocumentsCorePack to simplify and streamline business processes within Dynamics 365 and PowerApps.
Since DocumentsCorePack Service Version 2020.103 it is possible to use your existing One-Click-Actions not only in the context of the DocumentsCorePack Dialog but also directly in workflows and actions. Therefore, a new lookup field called OCA was implemented that can be found in the Advanced area of your AutoMergeWorkingItem record.
Figure 1: MSCRM-ADDONS.com AutomergeWorkingItem – Advanced tab
Use OCAs as part of a workflow
A quick and easy way to use the new feature is when creating an AutoMergeWorkingItem via a workflow or an action. We start by creating a new One-Click-Action.
Creating a new One-Click-Action: Open the DocumentsCorePack in your Dynamics 365 and navigate to the “One-Click-Action”-tab.
Please note: If you need further information on how to create an One-Click-Action, have a look at this article first.
In this very basic example, we simply define the template ❶ and the filetype ❷ via the OCA.
Figure 2: Create OCA
Create a workflow: Now it’s time to create our workflow. Create a new workflow and add an AutoMergeWorkingItem as part of your process step procedure.
Please note: If you need further information on workflows and the usage of DocumentsCorePack have a look at this article first.
❶ Open record and give it a Name,
❷ choose CreateDocument for AutoMergeAction
❸ and provide a PrimaryRecordUrl.
❹ Finally choose your One-Click-Action via the OCA field in the Advanced area. As our template and the filetype is already defined in the OCA, no further information is needed here.
That’s pretty much it. Save your changes and run your workflow.
Figure 3: Create new workflow
Usage and Limitations
One-Click-Actions have been developed to work in conjunction with the DocumentsCorePack Dialog, therefore not all features will work in a workflow scenario.
1. Template Settings
Supported:
❶ Template selection: Either select Predefine Template or Use Multipart.
❸ Conditional Template
Unsupported:
❷ Edit Template
(Allow User Selection is also not supported)
Figure 4: Template settings
2. Processing Settings
Supported:
❶ All filetypes
❷ Attach document: Only attach as note is supported
❸ Print document
❹ Print Copies
❺ Run workflow
❻ Run action
❼ Save to SharePoint
Figure 5: Processing settings
Please note: When running an action Parameters for the following entity types can be provided by the DocumentsCorePack Service and later used in the action:
Type: EntityReference
Entity: Entity of the record from where the Document Process is started (Account, Contact e.g.)
Type: EntityReference
Entity: MSCRM-ADDONS.com AutoMergeWorkingItems
Type: EntityRefence
Entity: Email, Appointment, Letter.
These activities will only work in some type of workflow scenarios. E.g.: create an activity in a previous workflow step and attach the document to the newly created record either via AttachToEmail, AttachToAppointment or AttachToLetter.
3. Review Settings
Figure 6: Review settings
Those features are typically designed to be used in conjunction with the DCP Dialog and are not supported in this kind of scenario.
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to support@mscrm-addons.com