I use the customresource WF_PROCESSLIST and WF_PROCESS_ATTRIBUTES to create a detailed job history list.
To do this, I have to loop through the table PROCESSLIST and with every row in this table I have to loop through the WF_PROCESS_ATTRIBUTES. The combined values are placed in a new table.
This workes fine until the amount of jobs increases. The forms responds slower and slower.
Is there another solution to create a detailed job history, without the loss of performance?
Detailed Job history
Moderators: Jon, Steve, Ian, Dave
-
- Ebase User
- Posts: 97
- Joined: Thu Sep 13, 2007 6:07 am
- Location: The Netherlands
- Wai
- Moderator
- Posts: 165
- Joined: Wed Sep 12, 2007 9:04 am
- Location: Sandy, UK
- Contact:
Have you had a look at the Workflow Administrator form? There is an Audit Trail and Job History in there.
There could be hundreds or thousands of jobs, and therefore there will always be performance issues with the way you are doing this.
I'm not sure how detailed your job list needs to be but it would be a good idea not to display all the process attributes in the list. It would be more efficient to only fetch the process attributes after you have selected a job to view.
There could be hundreds or thousands of jobs, and therefore there will always be performance issues with the way you are doing this.
I'm not sure how detailed your job list needs to be but it would be a good idea not to display all the process attributes in the list. It would be more efficient to only fetch the process attributes after you have selected a job to view.
0 x
-
- Ebase User
- Posts: 97
- Joined: Thu Sep 13, 2007 6:07 am
- Location: The Netherlands
I did take a look at the Workflow administrator.
We want our users to be able to view their request-history. When they submit a request they actually start a new job. I use a common process which is used by multiple forms (a form represents a certain request).
When you only fetch the job list, you only see something like this:
Now it is hard to find a specific request.
I want them to see the following:
Now it is easier to find a specific request. That way our users are able to view their request history and status of the request (status = task in the job).
We want our users to be able to view their request-history. When they submit a request they actually start a new job. I use a common process which is used by multiple forms (a form represents a certain request).
When you only fetch the job list, you only see something like this:
Code: Select all
***********************************************************
* Job id | Processname | Process description | .... *
***********************************************************
| id 1 | Process 1 | Description 1 | .... |
-----------------------------------------------------------
| id 2 | Process 2 | Description 2 | .... |
-----------------------------------------------------------
I want them to see the following:
Code: Select all
**********************************************
* Job id | Request | .... *
**********************************************
| id 1 | Request laptop | .... |
----------------------------------------------
| id 2 | Request exteranal email | .... |
----------------------------------------------
0 x
What's the meaning of Justice...
- Wai
- Moderator
- Posts: 165
- Joined: Wed Sep 12, 2007 9:04 am
- Location: Sandy, UK
- Contact:
One way you can do this is to make a slight amendment to the Jobs list. Using the existing Workflow Administrator Jobs list table as an example.
You can display your job details in the Process Description column by using field substitution into the Workflow Process Properties Description field.
for example:
- In your Workflow Process, click on the Edit Process Properties icon. In the General tab, you will notice a Description field. This field is actually the Process Description column you see on the Jobs list table.
- Add your process attributtes that provide details of the job to this field using field substitution (e.g Intake ID: &&@INTAKE_ID, Form: &&@FORM_NAME, Status: &&@STATUS).
You can then rename the column in the table from Process Description to Request.
You can display your job details in the Process Description column by using field substitution into the Workflow Process Properties Description field.
for example:
- In your Workflow Process, click on the Edit Process Properties icon. In the General tab, you will notice a Description field. This field is actually the Process Description column you see on the Jobs list table.
- Add your process attributtes that provide details of the job to this field using field substitution (e.g Intake ID: &&@INTAKE_ID, Form: &&@FORM_NAME, Status: &&@STATUS).
You can then rename the column in the table from Process Description to Request.
0 x
-
- Ebase User
- Posts: 97
- Joined: Thu Sep 13, 2007 6:07 am
- Location: The Netherlands
Who is online
Users browsing this forum: No registered users and 2 guests