Skip to main content
arthuro2392
December 20, 2023
Solved

[BUG] Appian Reverts Rich Text Item to previous version whenever it cannot find a CDT in its namespace

  • December 20, 2023
  • 5 replies
  • 0 views

Whenever theres's a CDT not found in the namespace it has been given, appian reverts its components to the previous version automatically:


- CDT with propper namespacing

- CDT without propper namespacing (notice the upper case PEOPLEFUNCTION at line 2 and the alert the interface is showing already)

- When we save the file, then the code changes the components to the previous version (notice richTextItem_18r1 at line 7):

This behavior works with Buttons and RichTextItems as far as we found it 

CODE for replicating it

a!localVariables(
  local!a: 'type!{urn:appian:ps:PEOPLEFUNCTION}SecurityRoleMap'(),
  {
    a!richTextDisplayField(
      labelPosition: "COLLAPSED",
      value: {
        a!richTextItem(
          text: "Some text",
          color: "ACCENT",
          size: "MEDIUM_PLUS",
          style: "STRONG"
        )
      }
    )
  }
)

Special thanks to: [mention:2817a4e7a26c4849b30fddb9463db79d:e9ed411860ed4f2ba0265705b8793d05] , [mention:2095d9df479a4cf8910364249d6fc9aa:e9ed411860ed4f2ba0265705b8793d05] , [mention:fa7ebd8f6bc24da585050ce7ad867501:e9ed411860ed4f2ba0265705b8793d05] 

Best answer by peter.lewis

Also just to follow up - this is a known issue and there is an existing knowledge base article for this issue: community.appian.com/.../kb-1917-system-rule-references-revert-to-deprecated-versions-of-system-rules

5 replies

stefanhelzle0001
Brainy
December 20, 2023

Did you open a support case to report this behaviour?

arthuro2392
December 20, 2023

Nope, don't have access to do it and it's difficult in the hierarquy I'm in rn. So, I've put it here to not lose the finding.

stefanhelzle0001
Brainy
December 20, 2023

[mention:6b9f80ff18f9420082d13ef2d5121d56:e9ed411860ed4f2ba0265705b8793d05] , can you help us with this?