Post a Request

A Role Processor with the Post role type posts a request to a target system after the Review role is finished.

When a Role Processor posts a request for the Post role, the request can be posted by:

  • The Integrate process assigned to the scenario (used when posting to SAP). Refer to Add a Process to a Scenario for more information.
  • Manual post. Refer to Use Manual Post for more information.
  • A custom posting process developed for a target system.

NOTE: Custom posting pages or processes are created and maintained by users.

Posting takes place on theRequest Group Post and Request Post Process pages, which are automatically assigned to any role with the role type of Post.

A post can be posted individually or as a group post, which posts each process in priority order. The lowest priority is posted first.

dspConduct™ updates the request status during the posting process.

A request moves to the Posting Started status when a Post role clicks the Post or Group Post icon on the Request Group Post and Request Post Process pages.  

A request moves to the Posted with Errors status when all Integrate processes associated with the request are finished processing and at least one posting process has failed.

A request moves to the Posted status when all Integrate processes associated with the request are finished processing and all postings are successful.

NOTE: When a Request is created, each Integrate Process assigned to the Scenario is assigned a unique Posting ID which can be used to assist while troubleshooting. Integrate uses this Posting ID as a parameter for Integrate Process Template rules and validations. The Integrate Process is also passed a Where Clause used for the posting data views that only contains the Request ID (e.g. “WHERE RequestID = 999”).

NOTE: After a request is finished, the Post role can be finished, during which the Final Finish process runs. The data that was posted is downloaded into target tables. Refer to Finish a Role with the Post Role Type, and Register Tables for Download as a Finish Process in dspConduct™.

NOTE: A post can be posted multiple times. The messages related to posting failure or success on the Request Post Message page displays information about the latest post.

NOTE: A setting can be configured to automatically post a request. Refer to Auto Post a Request for more information.

NOTE: A dependent scenario may exist in another category. Refer to Allow a Scenario to be used in Other Categories for more information.  When a business process uses a scenario from another category, the request that is created for that scenario will be created in the database/Webapp that is the default WebApp for that other category. For example, a category called Northwest Region has a default WebApp of NWRegion. It  contains a scenario called Create SoldTo – General Data. This scenario has been configured for use in the category US Operations. A scenario in US Operations is Create SoldTo. A user could create a business process in the US Operations category that uses the Create SoldTo scenario as a parent of the Create SoldTo – General Data scenario from the Northwest Region category. When the business process is executed, a request is created in the NWRegion WebApp.  

This section contains the following topics:

Post a Request

A Role Processor with the Post role type can post a request to a target system.

NOTE: Credentials must be detected to post data. The Credentials Detected check box on the Request Group Post page must be enabled. If it is disabled, set credentials. Refer to Add Stored Credentials as a User on a Page in Integrate for more information.

To post a request in dspConduct™:

  1. Click dspConduct > Requests in the Navigation pane.
  2. Click the Roles icon for a request.
  3. Click the Tasks icon for the post role.
  4. Click Request Post.
  5. Click the Group Post icon on the Request Group Post page to run each posting process listed on the Request Post Process page
  6. Click the Post icon for a process on the Request Post Process page.
  7. A confirmation message displays; click OK.
  8. After the Posting Status updates to Success or Failure, click the Message icon for each process to view details.

NOTE: A Designer can configure users to receive workflow notifications when the posting status is updated to Success or Failed. Refer to Send Workflow Notifications when a Post Fails or Succeeds for more information.

Continue with Finish a Role with the Post Role Type.

Auto Post a Request

A Designer can configure the Auto Post Role setting on the Scenario (Roles) page’s Vertical View, which allows a request to be automatically posted after all data dependencies have been completed, all validations have passed, and the Review role approves the request. In this case, a user assigned to the Post role does not click the Post button to initiate the posting.

Before performing this task a role with the Post role type must exist in the scenario. Refer to Add a Role to a Scenario for more information.

Refer to Post a Request Overview for general information.

If the request posts unsuccessfully the Post role must take further action, unless the Auto Finish Role setting is enabled for the Post role. In this case, the role automatically finishes with a status of Posted with Errors. Refer to Auto Finish a Role for more information.

NOTE: When using Auto Post, the Post Workflow Notification records at the specific Scenario’s Post role are used to determine which users receive posting success or failure notifications.

NOTE: The Auto Post Role feature can only be used if default credentials are set for all connections used by the scenario’s Integrate processes. Refer to Add a Process to a Scenario and Add Default User Credentials to a Connection for more information.

To enable the Auto Post Role setting for a scenario role with the Post role type:

  1. Select dspConduct > Design in the Navigation pane.

  2. Click the Scenarios icon for a category.

  3. Click the Roles icon.

  4. Click Vertical View for a role with the role type of Post.

  5. Click the Auto Post Role check box to enable it.

    NOTE: This check box only displays for roles with a role type of Post.

Use Manual Post

A user assigned to a role with a role type of ManualPost can use dspConduct™ workflow to track completion of tasks that are performed manually outside of dspConduct™.

A ManualPost role receives notification that work can be started, and finishes that work by using a custom post process or performing a physical task. When the task is complete, the ManualPost role user clicks Finish on the Request Role page. dspConduct™ only tracks the name of the user who clicked the button and the time the Finish button was clicked. There is no Integrate, Collect or dspConduct™ processing associated with the ManualPost role.

Depending on how the Business Process is configured, a dependent scenario may begin after the ManualPost role finishes.

Refer to Add a Dependent Scenario to a Scenario for more information.

Schedule a Post for a Specified Date and Time

A Role Processor with the Post role type can schedule a post to process at a date and time in the future.

Before a Role Processor can perform this task, a Designer must enable this feature at the role or scenario role level.

To schedule a post:

  1. Click dspConduct > Requests in the Navigation pane.
  2. Click the Roles icon for a request.
  3. Click the Tasks icon for the Post role.
  4. Click the Task ID.
  5. Click Edit.
  6. Click the Post Start Time field and select the date and time in the calendar.
  7. Click Save.
  8. Click Schedule Post.