DBohner-(db)
Legendary Poster
OK, I know this is well-beyond the normal...
I have a requirement to configure logic of a Child-App, based on the Parent App that calls it.
For example:
If AppX is called by App1, AppX does A, B, C...
If AppX is called by App2, AppX does C, D, X...
If AppX is called by App3, AppX does A, C, X...
What AppX does, based from the calling (Parent) app - is stored in a table...
Using a C-Function, I can usually identify the calling application based LPDS (I'll have to login to their system to confirm the structure)...
The function works 'most of the time', but when there are a cascade of parents calling down the line - the DS doesn't seem to populate correctly. Thus, I'm looking for an alternate suggestion.
In other words, What might be the Best way to identify 'what parent' called a Child App/Form?
Oh - Changing the FI Structure is not an option (that modification word comes into play, for some reason)...
(db)
I have a requirement to configure logic of a Child-App, based on the Parent App that calls it.
For example:
If AppX is called by App1, AppX does A, B, C...
If AppX is called by App2, AppX does C, D, X...
If AppX is called by App3, AppX does A, C, X...
What AppX does, based from the calling (Parent) app - is stored in a table...
Using a C-Function, I can usually identify the calling application based LPDS (I'll have to login to their system to confirm the structure)...
The function works 'most of the time', but when there are a cascade of parents calling down the line - the DS doesn't seem to populate correctly. Thus, I'm looking for an alternate suggestion.
In other words, What might be the Best way to identify 'what parent' called a Child App/Form?
Oh - Changing the FI Structure is not an option (that modification word comes into play, for some reason)...
(db)