hardcode values in paragraph field

RE: hardcode values in paragraph field

hema.mathivathanan — Tue, 18 Jul 2023 15:31:06 GMT

Thanks, I will use the value in the "submit" button

RE: hardcode values in paragraph field

juergeng0002 — Tue, 18 Jul 2023 15:29:32 GMT

Of course!
It is a question of logic - If there is something already in the field, you don't add the word 'Rejection' Only the first time.
You have to replace the value expression with this one:

 value: if(a!isNullOrEmpty(local!comment),"REJECTION " & local!comment,local!comment),

RE: hardcode values in paragraph field

Mike Schmitt — Tue, 18 Jul 2023 15:24:45 GMT

Yeah, i'll echo what Stefan said - you can manipulate the value of the user-entered text however you want AFTER the user is done with it. You don't NEED to have that extra text sitting inside the text entry box during user entry.

a!buttonWidget(
label: "Submit", /* for example */
submit: true(),
saveInto: {
ri!buttonClicked, /* for example */
a!save(ri!rejectionComment, "REJECTION " & local!comment)
}
)

RE: hardcode values in paragraph field

Stefan Helzle — Tue, 18 Jul 2023 15:22:11 GMT

Why not just add that word on submit?

RE: hardcode values in paragraph field

hema.mathivathanan — Tue, 18 Jul 2023 15:20:22 GMT

It's a requirement where we have "Rejection" followed by where the user can enter text. If I give value: "rejection" & local!comment, the user can delete the word "Rejection" or make changes to it. But, I need it to stay the same.

Do we have a way to do it

RE: hardcode values in paragraph field

Mike Schmitt — Tue, 18 Jul 2023 15:11:21 GMT

[quote userid="154541" url="~/discussions/f/user-interface/29385/hardcode-values-in-paragraph-field"]When I used the a!richtextdisplayfield[/quote]

because a!richTextDisplayField() is a read-only component.

[quote userid="154541" url="~/discussions/f/user-interface/29385/hardcode-values-in-paragraph-field"]value: "REJECTION " & local!comment,[/quote]

So if you were trying to make it a READ-ONLY paragraph field, this would be an OK way to DISPLAY the value. However it's a bit more tricky if you want the text to show up in the field as a default but then save only the user input that follows that value - because, when "REJECTION " is included in the "value" field, that text populates into the user entry, and then it flows to the saveInto when the user changes the value of the field, so any time the user touches it, it'll save a redundant "REJECTION " at the front of the message.

There are ways around this involving manual work inside the saving, but honestly I fear it's just going to cause more confusion.

This makes me ask though, why the redundant "REJECTION" label *inside* the field value? What's wrong with using the... "label" as the label? What value does it add to have the word again?

RE: hardcode values in paragraph field

juergeng0002 — Tue, 18 Jul 2023 15:11:16 GMT

Hi,
not sure what you are trying to accomplish. The issue with the above approach is, every time the user is interacting with the field, the word 'Rejection' will be added to the content of the field.

I see no issue with a rich text display field.

a!localVariables(
  local!comment,
  {
    a!paragraphField(
      label: "Rejection Comment",
      value: "REJECTION " & local!comment,
      saveInto: local!comment,
      
    ),
    a!richTextDisplayField(
      label: "Rich Text Display Field ",
      value: a!richTextItem(
        text: "REJECTION " & local!comment,
        style: "EMPHASIS",
        size: "MEDIUM_PLUS",
        color: "ACCENT"
      )
    )
  }
)