Request Processor (Window ID-203)

From iDempiere en
Jump to navigation Jump to search

Table of Contents

Window: Request Processor

Description: Define Request Processors

Help: The Request Processor Window allows you to define different processes that you want to occur and the frequency and timing of these processes A Request Processor can be just for a specific Request Type or for all.

Tab: Request Processor

Description: Request Processor

Help: The Request Processor Tab allows you to define processes that you want to occur and the frequency and timing of these processes. If no other user is found, the items are assigned to the supervisor. A Request Processor can be just for a specific Request Type or for all.

Request Processor - Request Processor - Window (iDempiere 1.0.0).png

Fields
Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. R_RequestProcessor.AD_Client_ID
numeric(10)
Table Direct
Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. R_RequestProcessor.AD_Org_ID
numeric(10)
Table Direct
Name Alphanumeric identifier of the entity The name of an entity (record) is used as an default search option in addition to the search key. The name is up to 60 characters in length. R_RequestProcessor.Name
character varying(60)
String
Description Optional short description of the record A description is limited to 255 characters. R_RequestProcessor.Description
character varying(255)
String
Active The record is active in the system There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.

There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.

R_RequestProcessor.IsActive
character(1)
Yes-No
Request Type Type of request (e.g. Inquiry, Complaint, ..) Request Types are used for processing and categorizing requests. Options are Account Inquiry, Warranty Issue, etc. R_RequestProcessor.R_RequestType_ID
numeric(10)
Table Direct
Schedule R_RequestProcessor.AD_Schedule_ID
numeric(10)
Table Direct
Alert after Days Due Send email alert after number of days due (0=no alerts) Send an email alert after the item is Due (after Date Next Action). If set to zero, no alert is sent. R_RequestProcessor.OverdueAlertDays
numeric(10)
Integer
Reminder Days Days between sending Reminder Emails for a due or inactive Document When a document is due for too long without activity, a reminder is sent. 0 means no reminders.

The Remind Days are the days when the next email reminder is sent.

R_RequestProcessor.RemindDays
numeric(10)
Integer
Escalate after Days Due Escalation to superior after number of due days (0 = no) The item will be escalated and assigned to the supervisor after the number of days over due. If 0, there is no escalation. R_RequestProcessor.OverdueAssignDays
numeric(10)
Integer
Supervisor Supervisor for this user/organization - used for escalation and approval The Supervisor indicates who will be used for forwarding and escalating issues for this user - or for approvals. R_RequestProcessor.Supervisor_ID
numeric(10)
Table
Inactivity Alert Days Send Alert when there is no activity after days (0= no alert) An email alert is sent when the request shows no activity for the number of days defined. R_RequestProcessor.InactivityAlertDays
numeric(10)
Integer
Days to keep Log Number of days to keep the log entries Older Log entries may be deleted R_RequestProcessor.KeepLogDays
numeric(10)
Integer
Date last run Date the process was last run. The Date Last Run indicates the last time that a process was run. R_RequestProcessor.DateLastRun
timestamp without time zone
Date+Time
Date next run Date the process will run next The Date Next Run indicates the next time this process will run. R_RequestProcessor.DateNextRun
timestamp without time zone
Date+Time

Tab: Routing

Description: Request Routing

Help: Define the sequence of request types and keywords and to whom the web and mail requests should be routed to. The keywords are separated by space, comma, semicolon, tab or new line. The first match wins (first request type then keyword.

Request Processor - Routing - Window (iDempiere 1.0.0).png

Fields
Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. R_RequestProcessor_Route.AD_Client_ID
numeric(10)
Table Direct
Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. R_RequestProcessor_Route.AD_Org_ID
numeric(10)
Table Direct
Request Processor Processor for Requests Processor for Requests R_RequestProcessor_Route.R_RequestProcessor_ID
numeric(10)
Table Direct
Active The record is active in the system There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reports.

There are two reasons for de-activating and not deleting records: (1) The system requires the record for audit purposes. (2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are invoices for this partner record existing. You de-activate the Business Partner and prevent that this record is used for future entries.

R_RequestProcessor_Route.IsActive
character(1)
Yes-No
Sequence Method of ordering records; lowest number comes first The Sequence indicates the order of records R_RequestProcessor_Route.SeqNo
numeric(10)
Integer
Request Type Type of request (e.g. Inquiry, Complaint, ..) Request Types are used for processing and categorizing requests. Options are Account Inquiry, Warranty Issue, etc. R_RequestProcessor_Route.R_RequestType_ID
numeric(10)
Table Direct
Keyword Case insensitive keyword Case insensitive keyword for matching. The individual keywords can be separated by space, comma, semicolon, tab or new line. Do not use filler words like "a", "the". At this point, there are NO text search operators like "or" and "and". R_RequestProcessor_Route.Keyword
character varying(60)
String
User/Contact User within the system - Internal or Business Partner Contact The User identifies a unique user in the system. This could be an internal user or a business partner contact R_RequestProcessor_Route.AD_User_ID
numeric(10)
Table Direct

Tab: Log

Description:

Help:

Request Processor - Log - Window (iDempiere 1.0.0).png

Fields
Name Description Help Technical Data
Client Client/Tenant for this installation. A Client is a company or a legal entity. You cannot share data between Clients. Tenant is a synonym for Client. R_RequestProcessorLog.AD_Client_ID
numeric(10)
Table Direct
Organization Organizational entity within client An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations. R_RequestProcessorLog.AD_Org_ID
numeric(10)
Table Direct
Request Processor Processor for Requests Processor for Requests R_RequestProcessorLog.R_RequestProcessor_ID
numeric(10)
Table Direct
Created Date this record was created The Created field indicates the date that this record was created. R_RequestProcessorLog.Created
timestamp without time zone
Date+Time
Summary Textual summary of this request The Summary allows free form text entry of a recap of this request. R_RequestProcessorLog.Summary
character varying(2000)
Text
Error An Error occurred in the execution R_RequestProcessorLog.IsError
character(1)
Yes-No
Reference Reference for this record The Reference displays the source document number. R_RequestProcessorLog.Reference
character varying(60)
String
Text Message Text Message R_RequestProcessorLog.TextMsg
character varying(2000)
Text
Description Optional short description of the record A description is limited to 255 characters. R_RequestProcessorLog.Description
character varying(255)
String


Contributions / Posts

Description of Request Processor in Server Mode

The Request Processor is a server process that runs according to the parameters given in this window.

It's divided in the following subprocesses:

Process EMail

Not implemented yet. Maybe is for integrating the EMail Request Processor in future.

Find Sales Rep

  • Find the requests (according to type) without Sales Representative (SalesRep_ID=0) and not processed (Processed='N')
  • It tries to obtain a sales representative according to:
    • First the routes (Request Type)
    • If there are no request type of it doesn't match, then the process evaluate the keywords against the request summary

On the log is recorded when a sales rep can't be found

Process Status

Change the status of requests to next status according to the parameters on "Request Status" when timeout is reached.

Process Requests

Fill the Due type according to the rules:

  • Scheduled when date next action < sysdate
  • Due when date next action > sysdate and < sysdate + tolerance (from request type)
  • Overdue when date next action + tolerance < sysdate

Send alerts for due and overdue requests, it takes account of the Remind Days and Overdue Alert Days.

Escalate the due requests according to "Overdue Assign Days"

  • Escalates to supervisor of assigned sales rep
  • If not exists, then escalates to supervisor of request processor

Send inactivity alerts according to "Inactivity Alert Days" and "Remind Days"

Process ECR

Beta Functionality, related to BOM Change Request.

Delete Old Request Log

Delete the registers from the processor log where "Keep Log Days" is reached.