I've tried using the Workbench to update a security cube rule file and found an issue between Workbench and Architect.

One of our security rules references the Groups dimension in the following format:

[ { '}Groups':'MEM1','}Groups':'MEM2' } ] = S: WRITE;

This format fails the validation check in Workbench but is OK in Architect. Workbench complains about the middle ":" chars.

[ '}Groups':'MEM1' ] = S: WRITE;

This format works OK in both.


Does anyone know if that rule format we are using is non standard or if it looks like a parsing error with the workbench interface? For the time being I've reverted to saving in Architect.

------------------------------
Chris Davidson
------------------------------

#PlanningAnalyticswithWatson

Hi Chris,

The syntax is incorrect, it should be

['}Groups':{'MEM1','MEM2'}] = S: 'WRITE' ;

I would expect when you save the rule in Architect using the rule syntax you presented to have generated an error in the server message log.

------------------------------
Simon Saul
------------------------------

Original Message:
Sent: Wed December 01, 2021 05:59 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

I've tried using the Workbench to update a security cube rule file and found an issue between Workbench and Architect.

One of our security rules references the Groups dimension in the following format:

[ { '}Groups':'MEM1','}Groups':'MEM2' } ] = S: WRITE;

This format fails the validation check in Workbench but is OK in Architect. Workbench complains about the middle ":" chars.

[ '}Groups':'MEM1' ] = S: WRITE;

This format works OK in both.


Does anyone know if that rule format we are using is non standard or if it looks like a parsing error with the workbench interface? For the time being I've reverted to saving in Architect.

------------------------------
Chris Davidson
------------------------------

#PlanningAnalyticswithWatson

Hi Simon,

Yeah that makes sense that the format of the syntax is off in the original but I've checked and no errors are thrown in Architect or the tm1server log. The rules are live and active on the server after the save.

It looks like Architect and the TM1 server accepts that format and I can't for the life of me remember why they were set up in that format but there is an inconsistency in behaviour which isn't ideal.

------------------------------
Chris Davidson
------------------------------

Original Message:
Sent: Wed December 01, 2021 06:05 AM
From: Simon Saul
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

Hi Chris,

The syntax is incorrect, it should be

['}Groups':{'MEM1','MEM2'}] = S: 'WRITE' ;

I would expect when you save the rule in Architect using the rule syntax you presented to have generated an error in the server message log.

------------------------------
Simon Saul

Original Message:
Sent: Wed December 01, 2021 05:59 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

I've tried using the Workbench to update a security cube rule file and found an issue between Workbench and Architect.

One of our security rules references the Groups dimension in the following format:

[ { '}Groups':'MEM1','}Groups':'MEM2' } ] = S: WRITE;

This format fails the validation check in Workbench but is OK in Architect. Workbench complains about the middle ":" chars.

[ '}Groups':'MEM1' ] = S: WRITE;

This format works OK in both.


Does anyone know if that rule format we are using is non standard or if it looks like a parsing error with the workbench interface? For the time being I've reverted to saving in Architect.

------------------------------
Chris Davidson
------------------------------

#PlanningAnalyticswithWatson

I agree there is an inconsistency, personally I've always used the syntax I mentioned, but the other syntax indeed works but is only accepted in Architect, not PAW. Question for the dev team perhaps...

------------------------------
Simon Saul
------------------------------

Original Message:
Sent: Wed December 01, 2021 06:26 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

Hi Simon,

Yeah that makes sense that the format of the syntax is off in the original but I've checked and no errors are thrown in Architect or the tm1server log. The rules are live and active on the server after the save.

It looks like Architect and the TM1 server accepts that format and I can't for the life of me remember why they were set up in that format but there is an inconsistency in behaviour which isn't ideal.

------------------------------
Chris Davidson

Original Message:
Sent: Wed December 01, 2021 06:05 AM
From: Simon Saul
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

Hi Chris,

The syntax is incorrect, it should be

['}Groups':{'MEM1','MEM2'}] = S: 'WRITE' ;

I would expect when you save the rule in Architect using the rule syntax you presented to have generated an error in the server message log.

------------------------------
Simon Saul

Original Message:
Sent: Wed December 01, 2021 05:59 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

I've tried using the Workbench to update a security cube rule file and found an issue between Workbench and Architect.

One of our security rules references the Groups dimension in the following format:

[ { '}Groups':'MEM1','}Groups':'MEM2' } ] = S: WRITE;

This format fails the validation check in Workbench but is OK in Architect. Workbench complains about the middle ":" chars.

[ '}Groups':'MEM1' ] = S: WRITE;

This format works OK in both.


Does anyone know if that rule format we are using is non standard or if it looks like a parsing error with the workbench interface? For the time being I've reverted to saving in Architect.

------------------------------
Chris Davidson
------------------------------

#PlanningAnalyticswithWatson

Hi Chris and Simon,
Thank you for spotting the discrepancy between WB and Architect, 
We'd investigate and make sure the correct code structure is documented and is consistent.

Best Regards,
Svetlana

------------------------------
Svetlana Pestsova
IBM Planning Analytics Product Manager
------------------------------

Original Message:
Sent: Wed December 01, 2021 07:21 AM
From: Simon Saul
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

I agree there is an inconsistency, personally I've always used the syntax I mentioned, but the other syntax indeed works but is only accepted in Architect, not PAW. Question for the dev team perhaps...

------------------------------
Simon Saul

Original Message:
Sent: Wed December 01, 2021 06:26 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

Hi Simon,

Yeah that makes sense that the format of the syntax is off in the original but I've checked and no errors are thrown in Architect or the tm1server log. The rules are live and active on the server after the save.

It looks like Architect and the TM1 server accepts that format and I can't for the life of me remember why they were set up in that format but there is an inconsistency in behaviour which isn't ideal.

------------------------------
Chris Davidson

Original Message:
Sent: Wed December 01, 2021 06:05 AM
From: Simon Saul
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

Hi Chris,

The syntax is incorrect, it should be

['}Groups':{'MEM1','MEM2'}] = S: 'WRITE' ;

I would expect when you save the rule in Architect using the rule syntax you presented to have generated an error in the server message log.

------------------------------
Simon Saul

Original Message:
Sent: Wed December 01, 2021 05:59 AM
From: Chris Davidson
Subject: PAW Workbench Security Rule Won't Save But OK in Architect

I've tried using the Workbench to update a security cube rule file and found an issue between Workbench and Architect.

One of our security rules references the Groups dimension in the following format:

[ { '}Groups':'MEM1','}Groups':'MEM2' } ] = S: WRITE;

This format fails the validation check in Workbench but is OK in Architect. Workbench complains about the middle ":" chars.

[ '}Groups':'MEM1' ] = S: WRITE;

This format works OK in both.


Does anyone know if that rule format we are using is non standard or if it looks like a parsing error with the workbench interface? For the time being I've reverted to saving in Architect.

------------------------------
Chris Davidson
------------------------------

#PlanningAnalyticswithWatson