Skip to main content
Kofax

ReadSoft: Documentation for Last person to change vs. WC Processor vs. Processor fields

Documentation for Last person to change vs. WC Processor vs. Processor fields
307155

Question / Problem: 

Is there any documentation that explains when the Last person to change field (/COCKPIT/SHDR_DISP/CH_USER) is updated vs the WC Processor (/COCKPIT/SHDR_DISP/WC_USER_DISP) and Processor (/COCKPIT/SHDR_DISP/CR_USER) fields (e.g., /cockpit/1 vs /cockpit/wc)?

What happens to the Last person to change field when a substitute makes a change (e.g., adds a note)?  Does it depend on what action the substitute takes?

Answer / Solution: 

There is no documentation for this, but below is how/when these fields change regardless of whether the user is a substitute.

Last person to change a record in PROCESS DIRECTOR (/COCKPIT/SHDR_DISP/CH_USER) is/is not updated based on the following:
If user executes changes to fields in tables /COCKPIT/THDR,  /COCKPIT/TACCT,  /COCKPIT/TACCAS (the 'document data' ), this user will be saved as the Last person to change.

If user modifies the workflow status (Sent Workflow / Approve / Reject), etc., this user will be be saved as the Last person to change.

If user forwards the document, this user will NOT be saved as the Last person to change.

If user creates a note in workflow, this user will NOT be saved as the Last person to change.


Processor display in WORK CYCLE (recode email) (/COCKPIT/SHDR_DISP/WC_USER_DISP) reflects the current/last user who is assigned to or who processed the document in a workflow.

Processor of PROCESS DIRECTOR document (/COCKPIT/SHDR_DISP/CR_USER) is never updated.  It is the user ID for the user that created the document. Normally you find here the technical User for the RFC connection that is used for the INVOICES transfer.

Applies to:  

Product Version Category
Process Director Accounts Payable All Information Request

 

Author:  Tena Dumestre

  • Was this article helpful?