Managing Master Data with webMethods OneData 10.5 | Managing Master Data with webMethods OneData | Implementing webMethods OneData | Using Change Request | What are Change Requests?
What are Change Requests?
Using the Change Request Inbox
If you do not have the privileges to edit object data yourself, you can submit a request for the change. OneData submits your change request to the data owner, application administrator, or other authorized users.
A change request is conceptually similar to a help desk ticket or a service request, but has features specific to data management. A change request can be generic or object-specific. This distinction is based on whether the change request contains an object and a column name. If the request contains an object or column, OneData creates an object-specific request. Otherwise, OneData creates a generic request. Change requests can be generated in both the Work Area or Release Area.
For object-specific requests, OneData assigns the selected object or column to the object owner by default. You can change the assignment to any other user before updating the change request. After updating a change request, you can only address the request to another user, but you cannot change the assignment. An assigned user can re-assign the change request to another user or change the subject.
In a generic request, you can enter details of the requested change in discussion messages within the request. The members of a request can use the discussion thread associated to a change request for communication purpose such as to elaborate on the request, ask questions, provide answers or explain the approval/rejection decision. You can post messages in the thread addressing to a specific user or to no user in particular. In the first case, the addressed user has the option to reply to this message when viewing the request. The addressed user can only post messages in the discussion thread.
Note: If the data change has a workflow rule associated with it, the change routes through all the designated approvers specified in the workflow rule before it migrates to the Release Area. If there is no workflow rule associated with a data change in an object, the change that the assigned user makes in the Work Area reflects immediately in Release Area.

Copyright © 2011-2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.