Use Redwood Template for ERES Approval Notifications and Approve Using Deferred Mode

In this demonstration, we will walk through the setup and execution of inventory transactions with E-signatures enabled, covering both in-line and deferred modes. We will cover the following topics: E-signature configuration setup, task configuration for InvManagementERESApprovalTask, configuring Electronic Signature Preferences using the Redwood UI. Supported transaction modes: in-line signature mode, deferred signature mode, available in both desktop and mobile UIs. Withdraw action: overview of Withdraw action available in Deferred mode for select transactions.

Let us begin by configuring E-signature approvals. Navigate to Setup and Maintenance work area and search for Manage Task Configurations for Supply Chain Management. This opens the BPM Worklist. In the BPM Worklist, search for InvManagementERESApproval Task. For this task, define the approvers as needed. Next, let us configure the electronic signature preferences.

To use the Redwood page, you have to enable the Redwood configure E-signature preferences offering. Once enabled, you can access Configure Electronic Signature Preferences page from the Setup and Maintenance work area. Use the Redwood Configure Electronic Signature preferences page to enable E-signatures for your organization. The Configure Electronic Signature Preferences setup page now allows organizations to enable E-signature functionality for seven Redwood inventory transactions. Once E-signature is enabled, these transactions must be approved before they can be processed.

For the new Redwood flows for the seven inventory transactions, the same transaction names are used as in the current setup. However, the ADF flows have been renamed with the classic pages suffix to distinguish them from the new Redwood transactions. Additionally, a new option has been introduced to choose between In-line and Deferred approval modes. This choice applies only to Redwood transactions.

Let me begin by demonstrating a miscellaneous receipt transaction using the In-line E-signature mode. This mode closely mirrors the behavior of ADF flows. In the In-line mode, the initiator remains on the transaction page after submitting it for approval. And they must wait for approver action. If the initiator navigates away from the page before the transaction is approved, the transaction is discarded.

When an organization is configured to use In-line E-signature, the primary action button is relabeled as Submit for Approval. After all the transaction details are entered in the miscellaneous transaction drawer, clicking Submit for Approval opens a panel draw. This displays E-signature details, source identifier, a preview or link to electronic PDF record, approval list with real-time approval status, and other supporting transaction information.

The current status of the transaction is Pending Approval. An approval notification is sent to the designated approvers. Initiator can click Refresh in the panel drawer to update the approval status in real time. Approvers access pending approvals from their work list or notifications icon. Upon opening the approval request, the following information is displayed. E-signature details, source identifier, a checkbox to confirm the review of electronic record, link or preview of the PDF record, additional supporting information.

Actions buttons, Approve or Reject, are enabled only once the checkbox is selected. Let me go ahead and approve this transaction. After all approvals complete their actions. Use the Refresh button to get the Updated status. The transaction status changes from Pending Approval to Approved. Submit and Close button becomes Active. Click Submit and Close button to commit the transaction. A toast message appears confirming successful receipt.

Now, let us explore the deferred E-signature mode, a new feature introduced with Redwood flows. For this item, the current on hand is 142 each. Let us perform miscellaneous receipt. In this mode, the primary action button is labeled as Submit for Approval. Once all transaction details are entered in the miscellaneous transaction drawer, click Done. Then click Submit for Approval. Upon submission, a toast message appears displaying the E-signature ID. This can be used for tracking or audit purposes.

The initiator is automatically exited from the transaction UI. The transaction enters a pending state until it is approved. The initiator can track approval progress via the action status tab. The approver receives a request and takes the necessary action. Once all approvals are complete, the transaction is automatically committed. No further action is required from the initiator. The on hand is increased by 10 each, bringing the total to 152 each.

Let us now perform the miscellaneous transaction from the mobile UI. Regardless of the signature type configured for the organization, mobile UIs always operate in Deferred mode. The primary action button is relabeled as Submit for Approval, which is similar to desktop behavior. After entering the transaction details, click Submit for Approval. A toast message appears displaying the E-signature ID. Once approved, the transaction is automatically posted. No further action is required from the initiator.

Let us now explore Withdraw action. A new Withdraw action is now available for select flows when operating in Deferred E-signature mode. This feature is applicable to the following transactions, Inventory lot update, inventory serial update, ship confirm. If a transaction is in Pending Approval status, only users with the appropriate privileges can perform the withdraw action. This capability is particularly useful when the transaction needs to be modified before resubmission or the approval process is delayed or stuck.

Let us take the case of float transaction. It has been submitted for approval. Once its status is marked as Pending Approval, a privileged user can choose to perform the Withdraw action. Upon performing the Withdraw action, the transactions approval status is reset. A toast message confirms the status reset. The transaction now becomes editable again and can be resubmitted for approval as needed. This concludes the demonstration. Thank you.