Requests are part of a business process that is initiated for various sequences of events in order to achieve an end result. There are various types of requests predefined in Exact Synergy Enterprise. Depending on the request type, requests can be used for various purposes such as workflows, apply for leave of absence, share information, communicate electronically, track projects and opportunities, or create appointments in the calendar. Requests that are used in a process flow template can be used to initiate process flows. Specially defined request types can also be used to automatically elevate a customer’s status.
In this update, we have given the freedom to system administrators to rename/edit and customize various types of request. For example, if your business is in construction, then you can rename and customize the request type actions and status based on your business needs. You can also decide which actions should be visible to whom. With this beneficial feature, you can work at ease with familiar terminology used in your business.
To create a request, go to one of these menu paths:
To rename/edit a request action and status:
See the following sample screen:
Note: By default, the language shown will be based on the language defined at Preferences or System/Setup/Settings - General/Preferences.
Note: When you click on the Workflow: Search - Request screen, you will also notice that the renamed action and status is displayed at the the section headers at the Workflow: Search - Customize screen.
Disclaimer: Despite the continued efforts of Exact to ensure that the information in this document is as complete and up-to-date as possible, Exact cannot warrant the correctness and/ or completeness and/or specific applicability of the published and/or requested information in this document. Exact shall not be liable for any direct, indirect, incidental, special or consequential damages, lost profits or for business interruption arising out of the use of this document. The extraction and use of information from this document remains at all times completely within the user’s own risk.
Document ID: 20.319.893, Last modified: 28-04-2010, Security Level: All - 0