NWBC Runtime Environment Patch Level 43 is released. It contains corrections both for NWBC for HTML, and for NWBC Runtime as well. For details please see Note 2087977, or the collection Note 1353538.

What I would like to emphasize here, is that the Note contains an announcement, that from Patch Level 44, the

ID representation of the NWBC navigation tree API is planned to be changed.

The OBJECT_ID and PARENT_ID fields are currently represented without leading zeroes:


<item>

<OBJECT_ID>3</OBJECT_ID>

<UNIQUE_ID>unique_id</UNIQUE_ID>

<PARENT_ID>1</PARENT_ID>

<AGR_NAME>role_name</AGR_NAME>

<ORIGIN_ID>2</ORIGIN_ID>

<MENU_LEVEL>01</MENU_LEVEL>

<REPORT_TYPE>FL</REPORT_TYPE>

<SORT_ORDER>1</SORT_ORDER>

<TEXT>text</TEXT>

<IS_TOP_LEVEL>X</IS_TOP_LEVEL>

</item>


but from Patch Level 44, leading zeroes will be used (type: NUM10): E.g. `0000000000`,`0000000001`,`0009999999`,`0009999998`.


As it is described in the Note, this is important, in case there are modifications of the CL_NWBC_RUNTIME35 class in your system or you created BADI implementations for NWBC or NWBC APIs such as IF_NWBC_RUNTIME=>GET_NAVIGATION_TREE or IF_NWBC_RUNTIME=>GET_NAVIGATION_TREES are called. With PL44, the new ID format will be used, and your code MAY BRAKE if the hardcoded IDs are not replaced with the new format!

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply