For many applications, exactly one party in a work object can be identified as a customer, who in some cases may be internal to the organization. The customer may be a person or an organization. Information about this customer may be typed in, or may arrive from a central customer master database or system.
Conventionally, the party role name "Customer" identifies a customer party in a work object.
Process Commander includes standard properties in the Work- class that your application can use to record facts about a customer:
Your application can use these optional properties to support searching or reporting by customer (but not for correspondence addressees). For example, the standard report Effort by Customer depends on values of pyCustomerEnterprise and pyCustomer.
In a work object, work party details are within an embedded Page
Group
property (Work-.pyWorkParty) and so the
properties cannot become exposed as columns in a database table.
Accordingly, instances of the Index-WorkPartyUri class
associate a work party (for example a customer, supplier, or employee)
with a work party role, facilitating searches by party. Alternatively,
your application can copy the few facts needed at the Work-
level from the work party details into the properties described above, to
support reporting or searching.
Customer Process Management, customer satisfaction, work party | |
Atlas — Standard properties in the Work- class |