Clarity Service Management

Expand all | Collapse all

grpmem custom column

Jump to Best Answer
  • 1.  grpmem custom column

    Posted 01-23-2018 02:55 PM

    we have added a custom column to grpmem table as follows: //////////////////////////////////////////////////////////////////////// // Factory: grpmem //////////////////////////////////////////////////////////////////////// OBJECT grpmem { ATTRIBUTES Group_Member { zorg SREL org // SRel_Attr_Entry grpmem.zorg SERVICE_PROVIDER_ELIGIBLE; }; }; 

     

     

     

    mycase is : I need to limit the view of categories depending on the groups that the logged user is a member of . 

    every category has an "Organization" field =>

    every Group has "Organization" field. so; 

     

    example=>

    grp1 (org=org1) 

    grp2(org=org2)

    grp3(org=org3) 

    Appcategory ( org=org1) 

    Emailcategory (org=org2) 

    Networkcategory (org=org3) 

     

    analyst1is member of ( grp1,grp2) 

    then analyst1 can view category( Email,Application) only ==> not Network because he is not memeber of grp3

     

     

     

    I

    I used the following Data Partition on "Prob_Category" table with "View" organization.[zorg]group_list.member IN (@root.id) but I faced error message : "AHD05800:Bad where clause. invalid constraint. Unable to resolve organization.[zorg]group_list.member." kindly advice



  • 2.  Re: grpmem custom column
    Best Answer

    Posted 01-29-2018 06:31 AM

    Hmmm.
    I think your data structure setup is not correct or at least incomplete.


    Your example shows it clearly:
    you assign organizations to your incident areas and to your Groups

    both relations are already existent: pcat.organization and grp.organization.

    I would not add an org SREL to the grpmem factory.

     

    The only thing missing from my Point of view, is a list attribute (BREL) which contains a list of groups belonging to an organization.

     

    OBJECT org {
        ATTRIBUTES usp_organization SECONDARY {
          org_group_list BREL grp organization;
        };
    };

     

    Your view constraint for pcat might then look like


    organization.org_group_list.member_list.member=@root.id

     

    this can be read as (from right to left):

     

    View all pcat's where the logged in user (@root.id)
    is a member of one of the groups (member_list.member)
    which are one of the groups (org_group_list)
    which do have the same organization as an incident area(organization).

    Hope that helps and works....
    Regards
    ......Michael