customer

For many applications, exactly one party in a work item 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 item.

Properties

PRPC includes standard properties in the Work- class that your application can use to record facts about a customer:

• Customer ID (.pyCustomer) — A customer identifier such as an account number
• Customer name (.pyCustomerName) — A name, limited to 32 characters
• Customer organization (.pyCustomerOrg) — The customer organization
• Customer enterprise (.pyCustomerEnterprise) — A parent or overall customer
• Customer level (.pyCusLevel) — For special categories of customers such as gold, platinum, high-net-worth, and so on.
• Customer satisfaction (.pyStatusCustomerSat) — To record the affect or disposition of the 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.

Reporting on work parties and looking up work parties

In a work item, 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.

Related terms

Open topic with navigation