Show
all
This topic describes the traditional ('fixed') WorkManager and WorkUser portals, introduced in V5.1. As a best practice in new applications, use a portal based on the composite User and Manager portals (introduced in V5.5), rather than the traditional portals. See About Composite Portals.
The My Process Actions area of the
WorkManager portal is available only to work managers. Use
this area to apply an action to all the assignments on a worklist or
workbasket. PROJ-342 This function is known as bulk
processing.B-15934 SR-6408 B-17617 SR-1797
C-424 For example, you can transfer assignments from one
operator (within your group) to another, from one workbasket to another,
or apply a flow action repeatedly to all the assignments on a worklist.
You can wait and watch as the system processes the assignments, or send
the processing to an agent that processes them in background mode.
To transfer
assignments from a worklist or workbasket
To transfer assignments in bulk:
- In the upper left area of the WorkManager portal,
select the work
pool name that contains the assignments to be processed.
- Select an operator from the left Transfer work
from drop-down list, or a workbasket from the right
Transfer Work from drop-down list. These list all
operators in a work group, or all workbaskets associated with a
work group. PROJ-352
- The workspace changes to present a list of assignments (in your
current work pool) for that operator or workbasket. Click a column
header to sort by that column. BUG-2157 BUG-7384 Indicate
which assignments to transferring using the Select All button, Deselect
All button, and checkboxes at the left of each row. (If
more than 500 assignments are found, the display is paged. Process
the first 500 assignments first, then click Process More Items to process those on the next page,
and so on.) 5.5 GRP-400 PROJ-1480
- In the Reassign action area, select a
destination operator or workbasket.
- Optionally, select the Run in background? box
to have this bulk processing performed in the background, by the
Pega-ProCom agent rather than in your current requestor session.
See About background processing.
PROJ-157
- Click Process Assignments. Foreground
processing may take minutes or more, depending on the number of
assignments to be processed. When processing completes, the system
redisplays with worklist with a check mark indicating each updated assignment, or an for assignments not updated. To access an error
message, hold the mouse pointer over the to
view a ToolTip.
- Optionally, click Process More Items
if there are more assignments to process.
To apply one flow
action to multiple assignments in a worklist
To apply a flow
action to multiple assignments in a workbasket
Bulk Process by Work Type
To process assignments by work type: GRP-2760
- In the upper left area of the WorkManager portal, select the work pool
name that contains the assignments to be processed.
- Locate the row containing the label Bulk Process by Work Type.
- Select one Work
Type from the drop-down list.
- At the Bulk Processing form, at the Create Operator field enter the first two letters of the Operator's name to get a list of results. Select an operator's name from the Create Operator
list.
- At the Update Operator field, enter the first two letters of the Operator's name to get a list of results. Select an update operator from the Update Operator list. Note that the operator fields use operator names and no ID's.
- Select a status from the Status list, for example
Resolved–Completed
.
- Select the Created After and Updated After dates.
- Click Update Filter to return search results.
- Results are listed below. Click the checkbox to select a specific result, or click the checkbox in the header to Select All. Click any of the tabs to sort by ID, Subject, Status, Update Operator, or Update Time.
Bulk Process Cover
To process assignments by cover: GRP-2760
- In the upper left area of the WorkManager portal, select the work pool
name that contains the assignments to be processed.
- Locate the row containing the label Bulk process cover.
- Select one Cover from the drop-down list, for example
Build a Product.
- Enter the first two letters of the Cover ID to get a list of results. Then Select a cover ID from the Cover ID
list.
- Click Process Cover
- All Work Objects in a Cover are displayed in the Bulk Processing screen.
Bulk Process Folder
To process assignments by folder: GRP-2760
- In the upper left area of the WorkManager portal, select the work pool
name that contains the assignments to be processed.
- Locate the row containing the label Bulk process folder.
- Select
Process Folder.
- Enter the first two letters of the Folder ID to get a list of results. Then Select a folder ID from the Folder ID list.
- Click Process Folder
- Results appear in the Bulk Processing screen.
About background
processing by the Pega-ProCom agent
If you need to transfer or process dozens or hundreds of
assignments, it may be preferable to send the processing for processing in the
background, and receive an email when the processing is complete.
The Pega-ProCom agent includes an activity that provides such
processing.
To use this facility:
- Review the Data-Agent-Queue instances on your
system; one for the Pega-ProCom agent exists on each node. Ensure
that the row identifying the AgentBulkProcessing
activity is enabled on at least one node, and that the overall
Enable this agent? box is selected for that
node.
- Ensure that an email account data instance
(Data-EmailAccount class) is defined to send email
from your application.
- For each manager who is to use this facility, ensure that a
valid email address is present in the Operator tab of the Operator ID form.
- Complete input values for one of the My Process
Actions facilities. Select the Run in Background check
box.
- Click Process Assignments. Background
processing may take minutes or hours, depending on the number of
assignments selected and other conditions.
- When background processing by the Pega-ProCom agent is
complete, the agent sends an email message listing the count of
assignments selected and processed, and a list of the keys of
assignments not processed. (Bulk processing skips assignments for
various reasons, including the inability to acquire a lock.)
How it works
When you click the Process Assignments button, the system creates
an instance of the Assign-Schedule-Future class, which
serves to notify the Pega-ProCom agent that a bulk processing request
is pending. It changes the owner of assignments to be processed to the
reserved value pyBulkProcessing
, so that they are no
longer on the original worklist or workbasket.
As it processes assignments, the Pega-ProCom agent temporarily
creates instances of the Assign-Schedule-InterimResults
class. When processing is complete, it forms and sends the email
message.
Notes
- Bulk processing is available only to users who hold the
standard privilege Work-.PerformBulk.
- These features (and the contents of the with
actions list) depend on the current work pool name and on
the flow actions available for each assignment. For example, after
you choose an operator in the Transfer work from
list, only assignments for that operator that include the standard
flow action Work-.Transfer (or a custom rule
overriding this standard rule) appear. B-4412
- Four standard system settings rules
(Rule-Admin-System-Settings rule type) affect
background bulk processing. You can override them with other
settings if necessary. See Atlas
— Standard System Settings rules.
- Bulk processing may detect problem
assignments. When this occurs, it sets the
Instruction field of such assignments to the text
value
Error: Bulk
.
- Some flow actions are not appropriate for bulk processing and
do not appear on the flow action list. (To mark a flow action as
inappropriate, select the Disqualify this action from bulk
processing? field on the Action tab of the Flow Action form.)
- On the work object history display, the phrase "system on
behalf of NAME" (where NAME is an operator full name)
indicates that bulk processing requested by that operator occurred
in background.
Improving
performance of bulk processing
If your system accesses the PegaRULES
database using a JDBC 2.0 driver, you may improve database update
performance by enabling an optional driver capability for batched
updates. PROJ-545 This benefit also applies to external
databases when accessed as external classes. DSILA
3/23/07
Not all JDBC 2.0 drivers correctly
implement this capability. As of May 2007, Pegasystems has verified
this capability with specific drivers including UDB 9.1 and Z/OS DB2.
Other vendors are reportedly addressing compliance. Contact Global
Customer Support for the latest information. ANILD 5/4/07
To allow Process Commander to use SQL prepared statements to batch
updates for improved performance on row inserts, updates, and
deletes:
- To enable this feature for every SQL database, add the
following line to the
prconfig.xml
file:
<env name="database\batchUpdates"
value="nn" />
where nn is
a positive integer setting a maximum count for the number of rows to
be batched.
- To enable this feature for a single SQL database that is
configured through the prconfig.xml file, add the
following line:
<env
name="database\databases\zzzzzz\batchUpdates"
value="nn" />
where nn is
a positive integer setting a maximum count for the number of rows to
be batched and zzzzzz is the name of the datasource. BUG-4825
(You can't use this option when the database is configured on the
Database form or through application server datasources.) DSILVA
5/10/07
- Redeploy and restart.
Typically, set a value between 5 and 30; vendor documentation and
experimentation may provide guidance for a good value. Setting this
value to 0 or 1 is equivalent to no batching.
When enabled, this feature applies to all processing —
including any Commit operations of two or more objects — but may
improve the performance of bulk processing by as much as 20
percent.
Portals in applications