nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Visual Format Edidor(VFE) fields check/validation.

mpal

How to check the length of Visual Format Edidor fields and search/replace patterns. We are using form API[js] for imposing validations on content

Find more posts tagged with

Comments

Jamik

I would suggest reading up on the FormsPublisher FormAPI documentation and also read up on how to use javascripts regular expression functions.

You should be able to do something like:


var field1 = IWDatacapture.getItem("/pathtofield/vfename").getValue();  // will set the value of field1 to be the datacapture field you specify
var length = field1.length;  //will get you the length of the string

IWDatacapture.getItem("/pathtofield/vfename").setValue(field1.replace(/test/g, "done")); // will change the current value with the new value that's replaced all word test with the word done

that's just an example i would suggest reading up on what I mentioned earlier to accomplish what you are looking to do. also do not post in multiple topics with the same question pick one topic and only post your question there.

Adam Stoller

How to check the length of Visual Format Edidor fields and search/replace patterns. We are using form API[js] for imposing validations on content

The length depends on whether or not you want to take into account the formatting in your calculations - i.e.: is <b>this</b> 4 characters or 11 characters or even 23 characters? (if you consider that '<' may be encoded as '<' and '>' as '>' - though I believe that if you reference the value of the item in FormAPI you'll get the '

's)

In FormAPI I believe you have to double-escape the escape sequences for match/replace regex's - i.e.

var x = y.replace(/\\s*,\\s*/g, ",");

Other than that there shouldn't be much of an issue for programmatic search/replace (which you may need to do if you don't want to count the formatting characters in the overall length of the value)

Keep in mind that length may vary considerably when dealing with language translations - in terms of both multi-byte characters and in terms of the number of characters it takes to write the same thing in different languages (e.g.: "goodbye" [7] or "bye" [3] vs. "ciao" [4] as an overly simplistic example) - so if you're dealing with length constraints for text and language translations - it's much more difficult to get it "right".