I want to know Significance of [ Generate Routing Table ] option in Application rule in Definition tab

General
, ,
1

Hello Experts,

Hope all doing good.

I want to know significance of Generate Route Table option we have in application. I know it does a lot behind scene but do not have clear understanding.

I found some interesting stuff like

  1. If there is some thing wrong with portal, views , landing pages - regenerating it solves the problem.
  2. If we are publishing custom component or view , pySyncToConstellation QP fails then regenerating solves the problem.
  3. Once we have regenerated table , after that if we are publishing component then QP does not fail.
  4. If during publishing component is not there in app static server then generating table creates that folder with component code.

Above and other behaviours we have seen with generating routing table which confusing us and not giving clear picture of its usage.

If any one can share any best documentation around generating routing table or Pega article would be helpful which can give low level details of functionality behind this.

Hoping to get expert advice asap.

Regards,

Shivam Garg

2

Hello @ShivamG17006319 We have used routing table in the context of generating semantic url to display the contents of Case A from say Case B which is in Constellation UI architecture. Both Case A and B are different case types.
The routing table plays a crucial role in organizing case types, data types, and landing pages.
Whenever a new case type or data type is created, a routing table is automatically generated in the currently used branch or the open ruleset version.
In the pyRoutingTable instance, under pyRoutes tag caseName is there to use to form the semantic url to view content of Case A. This ensures
that each case can be accessed directly through a meaningful, semantic URL.

Let me know if you would like to have more details on this use case.

Thanks,

Aditi

3

Thanks Aditi for sharing this. But I would like to know more with respect to context of custom dx components. I have explained the behaviour we have seen and how generating routing table is fixing that.

But interested in documentation or low level details , how it is fixing dx custom component related issues.

4

Its main purpose is to synchronize the application’s UI metadata with the internal mapping required for Semantic URLs and DX API calls. The routing table stored internally as the pyRoutingTable rule of type Rule-UI-Routing