expression to get the environmental URL

RE: expression to get the environmental URL

Navin Reddy — Fri, 31 Dec 2021 00:58:19 GMT

regexfirstmatch("https://[a-z]+\.[a-z]+\.[a-z]+",a!urlfortask(0))

RE: expression to get the environmental URL

ashish.deshmukh — Fri, 22 Sep 2017 04:59:46 GMT

If you are working on 17.x version, you can make use of Customization settings provided by Appian. Here you can mark the constants as environment specific constants and maintain those using Import Customization file. Refer below link for more details,
docs.appian.com/.../Application_Deployment_Guidelines.html

RE: expression to get the environmental URL

josep — Fri, 22 Sep 2017 02:12:52 GMT

Hi Alexandera,

When talking about environmental variables I would suggest to add a "{Company} Common Application" which can be setted and managed by the admin team. This is recomended for all the environment specific variables.

Best Regards
Jose P

RE: expression to get the environmental URL

Mike Schmitt — Thu, 21 Sep 2017 16:31:50 GMT

Of course this is now unnecessary in 17.1 and above - simply set environment constants as "environment specific", and then even re-importing a newer version of a constant won't overwrite the version currently on that environment.

RE: expression to get the environmental URL

alexandera — Thu, 21 Sep 2017 16:09:08 GMT

To avoid environmental constants from being overwritten by accident when deploying to higher environments, you can keep all of the environment dependent constants in a separate application, so when stories/applications/releases/bugs/etc. get deployed, the environment objects never get accidently deployed or overwritten. However, this means an extra step must be added to "deployment instructions" to handle manually editing environmental constants from one env to another.

RE: expression to get the environmental URL

josep — Wed, 20 Sep 2017 02:17:48 GMT

I would suggest to make a mix between a constant and this rule(concatenating rule!rule() & cons!APN_SITE_LINK), If you are thinking about sites that will absolutely work, even for task creating the link will be enough.
In case you need records there is an appian function to get them.

RE: expression to get the environmental URL

Satty — Tue, 19 Sep 2017 12:37:16 GMT

Thanks for that, but it is returning url till suite only, if i need entire UrL along with sub pages and parameter like;
www.appian123.ca/.../supplier-contact-registration

then, if anyone has any idea, do suggest

thanks

RE: expression to get the environmental URL

sam.zacks1 — Wed, 22 Mar 2017 18:03:55 GMT

Additionally you can create a constant and point directly to the user record since it will always exist in the application.

RE: expression to get the environmental URL

garethm — Wed, 25 Jan 2017 11:22:45 GMT

Thanks - much more comfortable using this than a deprecated function.

RE: expression to get the environmental URL

Puspendu Pal — Tue, 24 Jan 2017 14:07:55 GMT

If you dont want to use the deprecated method, you may try to get the base URL(xx.yy.com) using urlforrecord as follows:

with(
local!anyURL: urlforrecord(
recordType: ri!recordType,
identifier: ri!recordIdentifier
),
left(local!anyURL,search("/suite",local!anyURL))
)

RE: expression to get the environmental URL

Tim — Tue, 24 Jan 2017 10:22:56 GMT

Its always a rick using a deprecated function. The environment constants should be in a standalone app with a description that states they should only be deployed once and that app excluded from the dependency checks on other apps. Relies on people reading instructions of course ;-)

RE: expression to get the environmental URL

garethm — Tue, 24 Jan 2017 10:00:21 GMT

Hiya Tim
We had that system (constant, array constant and a choose statement which you set up for us!)... but the environmental constant can be easily overwritten by accident which changes the behaviour of the site - not by me I hasten to add!

So I was looking for a more fool-proof way to identify the environment and use that instead.

rule!APN_getSiteUrl() seems to work nicely...just hoping that the deprecated nature does not come back to haunt me!

Gareth

RE: expression to get the environmental URL

Tim — Tue, 24 Jan 2017 09:54:41 GMT

Hi Gareth! You consider having an application that contains constants to store these values and then deploying and modifying per instance for your environments. These can be very useful for things such as dynamic WSDLs.

RE: expression to get the environmental URL

Josh — Mon, 23 Jan 2017 21:07:56 GMT

note that rule!APN_getSiteUrl() uses fn!linktodocument() which has been deprecated and may be removed in a future release.

RE: expression to get the environmental URL

garethm — Mon, 23 Jan 2017 18:38:26 GMT

Thanks - perfect!

RE: expression to get the environmental URL

Ram — Mon, 23 Jan 2017 18:34:19 GMT

Hi Gareth,

rule!APN_getSiteUrl() might solve your problem. Hope this helps