Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Great news for all channel managers! It is now easier to sync various Settings with downstream organizations. To name a few, channel managers can now sync equipment and usage settings. This feature would help ensure that channel managers can equip downstream organizations with the settings they would need to create jobs that comply with the channel manager’s criteria.

...

  • Project Phase Settings: Equipment Settings, Adders, Default Costs, and Estimated Installation Dates

  • Usage Phase Settings: Persona Inventory and Utility Rate Escalation

  • Organization Settings: Organization Logo and Licences (note that this is only applicable to new organization invites).

  • Proposal Settings: Expiration Dates, Comparable Values, and Proposal Email

Note: The Proposal Templates are not included in the Data Sync’s features, as we already allow upstream organizations to share their templates with all downstream organizations.

  • Organization Settings: Organization Logo and Licences (note that this is only applicable to new organization invites).

Note: The Also, the following Settings will not be affected by the data sync feature:

  • Integrations and Integration Settings,

  • Feature Settings,

  • Financing Product Settings,

  • Operations Workflows,

  • Qualifications,

  • User Settings/Notifications.

To put simply, turning the Data sync feature will not affect these Settings in any way for both the channel managers and their channel partners.

How can I predict how Settings will be synced?

The flags shown above is a good introduction to how the Data Sync will behave. Now, we will give example scenarios and help you understand how pre-determined

  • Talk about how different Settings sync would be with varying flag variations (strict relationship (allow edit, don’t allow to edit); thinking if I should put this in a table.

RANDOM THOUGHTS, VERIFY ON ENGINE:

All INEXCLUSIVE relationships will sync/match for newly added orgs, and be Union or NA for all other changes.

All exclusive FLEXIBLE relationships will sync/match for newly added orgs, and be union or NA for all other changes

All exclusive STRICT relationships will sync/match for all cases EXCEPT FOR: data added post partnership [???] will verify

actions/changes:

newly invited org

new partnership with an EXISTING org

data added post partnership

data UPDATED post partnership

  • Give examples with screenshots