Many solutions require that the role is set to a particular value, such as "supplier" or "customer", to match the expected partner selection configuration.
This can be achieved by setting within a Camunda model a role-level property of
${partnerRole,partner}
This means "search for a partnerRole at lower levels of precedence, and if not found, use 'partner'". This can be overridden by setting the global property "partner.role" to the required role. You should also set "role.path" to "@{data:init.connectionPaths.role}", to allow processes to be sent to specific folders at the partner end. For example, if your want your partner role to be supplier, set properties like this (in addition to any other properties you need to set).
{ "global": { "partnerRole": "supplier", "supplier.path": "@{data:init.connectionPaths.supplier}" } }