Resources and TIBCO BPM Enterprise

Any Resources that you have defined are not exported to TIBCO BPM Enterprise, 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 TIBCO BPM Enterprise.

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.
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 TIBCO BPM Enterprise after deployment.