richTextItem, safeLink issue

RE: richTextItem, safeLink issue

swapnar6405 — Wed, 31 May 2023 00:36:11 GMT

Thank you all for your suggestions. Really appreciate.

RE: richTextItem, safeLink issue

Mathieu Drouin — Tue, 30 May 2023 16:59:50 GMT

To simplify the data entry of a fully qualified url, I would simply replace any existing occurrences with an empty string and then normalize it at the end. You should also validate it to make sure it is a valid URL, I would suggest using a regular expression for this. https://community.appian.com/b/appmarket/posts/regular-expression-functions.

a!localVariables(
  local!value: "https://google.com",
  concat(
    "https://",
    reduce(
      fn!substitute,
      local!value,
      merge({ "http://", "https://" }, { "", "" })
    )
  )
)

RE: richTextItem, safeLink issue

Mike Schmitt — Tue, 30 May 2023 16:29:23 GMT

You will need to verify it one way or another - there are numerous Appian text functions which you could use to do this, depending on how strong the need will be - you could use like(), left(), regexMatch, etc.

RE: richTextItem, safeLink issue

swapnar6405 — Tue, 30 May 2023 15:56:53 GMT

I have to find whether user entered "http://" or "https://" then in this case also, I can use like() function?

RE: richTextItem, safeLink issue

Harshit Bumb (Appyzie) — Tue, 30 May 2023 15:25:21 GMT

But before you do this, make sure to check if the URL already consists of this. You can do this using like() function.

RE: richTextItem, safeLink issue

Stefan Helzle — Tue, 30 May 2023 15:21:25 GMT

concat("https://", local!yourUrl)

RE: richTextItem, safeLink issue

swapnar6405 — Tue, 30 May 2023 15:19:57 GMT

How to insist that a fully qualified url entered by the user. Is there a way to use any kind of function to do this in Appian.

RE: richTextItem, safeLink issue

swapnar6405 — Tue, 30 May 2023 15:18:19 GMT

ERROR Details:

An Error Has Occurred The record view does not exist or you do not have permission to see it. (APNX-1-4205-015).

Users may enter or may not enter http// or https://, because of free text field.

RE: richTextItem, safeLink issue

Stewart Burchell — Tue, 30 May 2023 14:46:56 GMT

I believe you need the full URL e.g. for your example this needs to be: https://www.google.co.uk/.

You'll need to examine the value entered by a user and validate it (which you should be doing anyway) and perhaps add the https:// prefix if they haven't already provided it. Or you could simply insist that a fully qualified url is provided.

RE: richTextItem, safeLink issue

Mike Schmitt — Tue, 30 May 2023 14:00:10 GMT

[quote userid="170215" url="~/discussions/f/new-to-appian/28821/richtextitem-safelink-issue"]they came to the link and hit it is throwing an error.[/quote]

I don't have many suggestions without first knowing some detail about the error message the user is getting. Why not post the error text and/or a screenshot at least?

The two things I can think of in advance: 1) are you doing any sort of verification that the user is typing a valid URL? 2 ) Are you appending "http://" (etc) to the beginning of the URL being supplied, or are you assuming they'll type it?