Legacy platform

User interface validation for open form widgets

In the application, we have a certain guidelines based on business use-cases, where certain types of fields are considered as open form fields and are put in bypass of Input Validation.

Guidelines:
  • Any description field in the UI such as PriceMatchDescription, ItemDesc, and so on, are considered as open form fields.
  • Any instruction field such as InstructionText is considered as an open form field.
  • Any field that contains notes logged by the Sterling™ Store Engagement (Legacy) user or any other user such as the NoteText field is an open form field.
  • List of Open Form Fields in the application are as follows:
    • CodeLongDescription
    • Description
    • Keywords
    • ManufacturerItemDesc
    • InstructionText
    • ExtendedDescription
    • Message
    • LongDescription
    • TemplateXml
    • Format
    • Template
    • CategoryDomain.Description
    • CategoryDomainList.CategoryDomain.Description
    • CategoryList.Category.Description
    • Category.Description
    • TransformationHeader.Description
    • PricingRule.Description
    • PricelistHeader.Description
    • ItemList.Item.PrimaryInformation.Description
    • EntitlementRule.Description
    • Asset.Description
    • TransformationHeader.TransformationHeaderLocaleList.TransformationHeaderLocale.Description
    • TransformationConfig.Description
    • Order.Notes.Note.NoteText
    • Customer.NoteList.Note.NoteText
    • Note.NoteText
    • Inbox.DetailDescription
    • Inbox.InboxReferencesList.InboxReferences.Value
    • Order.TrackingInfoList.TrackingInfo.TrackingUrl
    • ExtendedDisplayDescription
    • ChargeNameDescription
    • ChargeCategoryDescription
    • PriceMatchDescription
    • ItemDesc