Skip to Content

How to use the cascader role option

Dear Experts,

Does anyone have used the cascader-role opt-in feature for a Goal Plan Template? I trying to follow the instructions described in the Implementation Guide for Goal Management (Unit 6.5 page 105, in Q4 2017 version) it says: When the "cascader-role” is enabled, the “cascader” role controls what field can be seen and edited and what table actions are permitted for the user who is cascading their goal. But I'm not sure how to configure this.

I would really appreciate any guidance on this.

Regards,

Carolina Lopez

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Apr 17 at 11:47 PM

    Hi,

    I used Cascader role option in permissions for a customer recently. The issue was that when a manager was creating a goal for his/her direct reports, permissions were working fine with some fields as read only and some fields which can be edited. But when same manager was cascading goals, he/she was able to edit all fields irrespective of permission specified in goal plan template. To enable Cascader role, we have to add <switch for="cascader-role" value="on" /> in <switches> block of goal plan xml (attached snapshot). There can be some other switches turned on in the goal plan xml(in my case one related to CPM). Ignore them and just add a line for this cascader role.

    <obj-plan-due>12/31/2018</obj-plan-due>
    <switches>
    <switch for="cascader-role" value="on" />
    <switch for="continuouspm-integration" value="on" />
    </switches>
    <text-replacement for="Instructions">

    .........

    Later use cascader role in permission block in same manner as we use E, EM+ etc. I just added cascader role in both read and write permission blocks(attached snapshot) so that permissions are consistent for both new and cascaded goals for all roles.

    <field-permission type="write">
    <description><![CDATA[E, F, EM and Cascader can write to these fields]]></description>
    <role-name><![CDATA[E]]></role-name>
    <role-name><![CDATA[EM]]></role-name>
    <role-name><![CDATA[F]]></role-name>
    <role-name><![CDATA[cascader]]></role-name>
    <field refid="name"/>
    <field refid="desc"/>
    <field refid="milestones"/>
    <field refid="Add_1"/>
    <field refid="Add_2"/>
    <field refid="Add_3"/>
    </field-permission>
    <field-permission type="read">
    <description><![CDATA[E, EM+, F, EX and Cascader can read these fields]]></description>
    <role-name><![CDATA[E]]></role-name>
    <role-name><![CDATA[EM+]]></role-name>
    <role-name><![CDATA[F]]></role-name>
    <role-name><![CDATA[EX]]></role-name>
    <role-name><![CDATA[cascader]]></role-name>
    <field refid="name"/>
    <field refid="desc"/>
    <field refid="milestones"/>
    <field refid="Add_Cat"/>
    <field refid="Add_1"/>
    <field refid="Add_2"/>
    <field refid="Add_3"/>
    </field-permission>

    Add comment
    10|10000 characters needed characters exceeded

    • Thansk a lot Aditya Kushwah for your answer, just have a question and is regarding the employee who receives the cascaded goal. In the request that I have, the client wants that the manager cascade the goal (with write permissions for all fields) but they want that the employee has just read permissions to this type of goal. I mean if as employee I create the goal I will have written permissions over that goal, but if was my manager who cascaded a goal into my plan I cannot edit or delete that goal. Is this possible, using this feature? in your case how works?

      Regards,

      Carolina