Pawel: You've asked two questions. Let me answer the second one first.

When you see (Available, Circumstanced) in the rule header, it means that the rule has been circumstanced. It doesn't indicate whether the rule you're looking at is either the base rule or the circumstanced rule. To do that, you need to click on the Circumstanced link in the header.

Circumstancing requires a base rule as well as a circumstanced version. Without a circumstanced version, the base rule is the only rule, but without a base rule, circumstancing won't work, because the system can't identify a fall-back candidate in the event that the circumstance isn't met. This is why the system won't let you delete certain rules; they're identified as base rules.

You first question requires a little more effort to answer. I'll see if I can't provide you with the information you need shortly.

Hi TEIXS, 

many thanks for your answer.

If comes to the first question, this kind of issues have happened not only to me, I know from my colleagues they also had difficulties to complete this exercise. So any further information, guidance on this is highly appreciated.

I think we can even have short screen sharing (gotomeeting) session where can cover this topic. And then can try to create a short footage showing how to proceed with the excercise. It should not take much time and for sure will be beneficial for new users.

Thanks, 

Pawel

To complete the Circumstancing exercise you need to perform the following steps:

1. Create a Circumstance Template. The Circumstance Template should list the .Employee.MaritalStatus property, as this is the property you want to test.
2. Create a Circumstance Definition. The Circumstance Definition should contain a table with one column, labelled Marital Status, and two rows: one containing the value "Married", and the other containing the value "Domestic Partnership". These are the values for which the circumstanced rule is applied, rather than the base rule.
3. Circumstance the SelectBenefits section, using the template and definition you created in the first two steps. Do not change anything on this rule, as it already satisfies the scenario: If the employee is married or in a domestic partnership, they are allowed to waive medical coverage (so long as their spouse/partner provides coverage for them).
4. Edit the base SelectBenefits section rule, to remove the checkbox for waiving medical coverage. Remember, this is the rule used if the circumstance (employee is married or in a domestic parnership) does not apply. In this case, the employee cannot waive coverage, so the checkbox is not presented on the UI.

Having said all that, this is a bit of a contrived example to demonstrate circumstancing. You could create a When rule to test the .MaritalStatus property, and use the Visible When field on the properties panel for the checkbox to not present the checkbox on the UI when the employee is single. (This is the second Alternative Design approach in the solution document.)