What are 'Dependencies'?

What is a dependency?

A dependency is simply a rule that is enforced to restrict the addition of items without the relevant prerequisites.

Dependencies can be used in a variety of ways, for example:

• ‘Add Ons’ - Some membership types may require specific attributes in order to be 'Current', for example, a ‘Coach Membership’ may require a valid ‘Background Screening' (DBS is the UK equivalent). So, the rule enforced would be that you must have this certification added to your profile before your membership is 'Current'.

• Roles - Some roles at an organisation may require upholding certain qualifications, for example: A ‘Club Coach’ must have a valid ‘Coach Certification’ and 'Individual Membership'. The user will not be able to access the Organisation for which their role entitle them access to until they have met the relevant prerequisites of their role.

• Event Entry - An example of a dependency taking effect is restricting an event entry because the user doesn’t have the correct membership for that event.

How does a dependency work?

Dependencies in the platform work in two main ways:

• This will allow you to add an item but this will immediately go into a ‘suspended/ Action Required’ status until the other item(s) added

• Prevent the addition of an item until the other item(s) are added.

Each add on (certification, membership etc) is configured in its own unique way so there is no 'one size fits all'. 

‘Add Ons’

‘Add Ons’ that have dependencies can be added to a profile but the item will remain in an ‘Action Required’ status until all the prerequisites are met. If you click the ‘Action Required’ status button it will display the required items.

Roles of an Organisation:

If a role has a dependency this will work similarly to a ‘Add On’ the role will appear on the profile, but the item will remain in an ‘Action Required’ status until all the prerequisites are met.

The user will not be able to access the Organisation account until the the prerequisites are met and this is in a ‘Current’ status on the profile. The photo below will provide an example of what the individual will be faced with if they try to access the Organisation without meeting the prerequisites.

If an event entry has a dependency the user will be able to progress through the entry form but upon 'Checkout', if a user doesn’t have the relevant dependency a pop-up will appear to display that the user must have the dependencies before they can enter.