@Roshan0001 it is probably a permission issue, admin will need to grant the appropriate projection in Aurena.

Thanks 

I can’t see that folder in a demo environment (Apps 10 Update 16), so I assume it’s either 1) a navigator configuration, 2) an extension or 3) a customisation.

If you open the a form under it and go to the System Info panel, what component and LU does it say?

Finally, are you logging into Aurena as application owner? If not, go to a permission set, the Projections and Lobby Pages sub-page and click iManage by Navigator].

Is the folder available to grant from there?

If not, the extension/customization probably isn’t developed for Aurena. More than 90% of IFS Applications 10 is, but not everything.

Hi , I have admin access and How to know the exact projection that related to above module?

I can’t see that folder in a demo environment (Apps 10 Update 16), so I assume it’s either 1) a navigator configuration, 2) an extension or 3) a customisation.

If you open the a form under it and go to the System Info panel, what component and LU does it say?

Finally, are you logging into Aurena as application owner? If not, go to a permission set, the Projections and Lobby Pages sub-page and click iManage by Navigator].

Is the folder available to grant from there?

If not, the extension/customization probably isn’t developed for Aurena. More than 90% of IFS Applications 10 is, but not everything.

Hi,

Thanks for the reply

bellow is the data from system info panel

Component:    ORDER

Logical Unit:    CRegulatory

I can’t find item in aurena navigator  tree, actually my requirement is integrate power app and regulatory module, via IFS API.
that means no API endpoint for regulatory in IFS API right?

Actually, there’s one possibility that I didn’t consider at first; it could be a Custom Logical Unit. What does the View and Package say in the System Info panel? Do they finish with _CLV and _CLP respectively?

Do you have access to the Solution Manager? If it is a custom LU and you have Solution Manager access, search custom logical units for LU Name: CRegulatory and check if “Create Projection” is ticked. If so, the API name is CustomProjectionCRegulatory.

If not, you can tick it and synchronise, or if you need it on the integration endpoint, configure a new projection:

1. Got to Aurena and launch Solution Manager > Application Configurations > Manage Projections > New Projection Configuration.
2. Choose “Create New Projection” and click Next.
3. Enter Custom Projection Name e.g. CRegulatoryHandling for a user facing API or CRegulatoryService for an integration API.
4. Pick Category = Users or Integration, whichever applicable.
5. Enter a short and sweet description and click Next.
6. Click new t+] and enter CRegulatory as Entity Name
7. Changed Operations Allowed if you need to be able to update.
8. Tick approved.
9. Then click .Done] and TNext] and click through the next two steps.
10. Publish on last step.

Actually, there’s one possibility that I didn’t consider at first; it could be a Custom Logical Unit. What does the View and Package say in the System Info panel? Do they finish with _CLV and _CLP respectively?

Do you have access to the Solution Manager? If it is a custom LU and you have Solution Manager access, search custom logical units for LU Name: CRegulatory and check if “Create Projection” is ticked. If so, the API name is CustomProjectionCRegulatory.

If not, you can tick it and synchronise, or if you need it on the integration endpoint, configure a new projection:

1. Got to Aurena and launch Solution Manager > Application Configurations > Manage Projections > New Projection Configuration.
2. Choose “Create New Projection” and click Next.
3. Enter Custom Projection Name e.g. CRegulatoryHandling for a user facing API or CRegulatoryService for an integration API.
4. Pick Category = Users or Integration, whichever applicable.
5. Enter a short and sweet description and click Next.
6. Click new .+] and enter CRegulatory as Entity Name
7. Changed Operations Allowed if you need to be able to update.
8. Tick approved.
9. Then click
10. Publish on last step.

 

View and Package name is &AO.C_REGULATORY, &AO.C_REGULATORY_API respectively.

Yes i have Solution manager access and according to your advice i have check the "CRegulatory" inside custom Logical Unit but i couldn't found the module.

That view and package name means it is a Customization or Extension delivered by IFS, i.e. code changed, rather than a  Custom Logical Unit that has been configured. It is likely that Aurena was deliberately excluded from that change, but you’d have to contact your IFS consulting organization or implementation partner to get those details.

Thanks Anders!