When creating an intuitive URL from an external system the documentation says to

Jin Pheh

Certified Associate Developer

over 9 years ago

When creating an intuitive URL from an external system the documentation says to use a Record opaque ID as the last parameter. If the record is entity backed this would correspond to the primary key of the entity correct?
If so can anybody spot check this url? When clicking on it users are being taken to the all record view instead of the specific record summary dashboard:
https://.../suite/tempo/records/property/75...

Discussion posts and replies are publicly visible

Parents

0 Jin Pheh
Certified Associate Developer
over 9 years ago

I'm not sure I follow what you mean by 'urlStub'. The record type I'm trying to link to is 'property' (already part of the url) and the documentation makes no reference to anyother URL parameters that need to be part of the string.

The URL created by urlforrecord is: https://.../suite/tempo/records/type/property/item/<appian-itemId>/view/summary
which doesn't use any other identifiers.

Also, because these links are being generated in an external system we don't have access to the urlforrecord expression.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Jin Pheh
Certified Associate Developer
over 9 years ago

I'm not sure I follow what you mean by 'urlStub'. The record type I'm trying to link to is 'property' (already part of the url) and the documentation makes no reference to anyother URL parameters that need to be part of the string.

The URL created by urlforrecord is: https://.../suite/tempo/records/type/property/item/<appian-itemId>/view/summary
which doesn't use any other identifiers.

Also, because these links are being generated in an external system we don't have access to the urlforrecord expression.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data