Resources and BPM

Any Resources that you have defined are not exported to BPM, and are not used at runtime.

Note: The only exception to this is that the Human Resource type, and any attributes defined for it, are exported to BPM.

Therefore, a Human Resource type must always be present in the Schema. Even if you choose not to include the standard Types in your Schema, a Human Resource type is always present, and it cannot be deleted from the Schema.

Resources are mapped to entities in the organization model using the Organization Browser. You can:

  • Map BPM Resources, which represent actual user IDs obtained from an LDAP-compliant directory, to Positions and Groups in the organization model,
  • Map attributes assigned to the organization model’s Human Resource Type to LDAP attributes in the LDAP sources you have used.

There are two Organization Browsers, one that is used if you are using the Openspace client, and another that is used if you are using a Workspace client (or custom WCC client). See the appropriate TIBCO Organization Browser User's Guide for your client.

Note: This means that any sort of information that you have reflected in defining Resources within Organization Modeler, including for example if you have used Resources to represent anything other than users, will not be represented in BPM after deployment.