Process design, forms & approvals — found from sitemap — Appian

Cited by

Facts read from this source

• Versioning manifest versions Report an error

  “When you create the connected system plug-in manifest, you define one version for the entire plug-in (in plugin-info) and separate versions for each connected system. There's no direct dependency between the two version types.”

• Versioning increment required Report an error

  “The plug-in version must be incremented with each release (no matter how minor) in order for the newer version to be deployed over prior releases.”

• Versioning major version behavior Report an error

  “When you deploy a new major version of your connected system, Appian retains the behavior of the existing connected systems and integrations. Integrations will continue to use the prior version of your connected system and their behavior won't change.”

• Versioning major version limit Report an error

  “There's no limit to the number of major versions you can create for your connected system, integration, or client API templates.”

• Versioning minor auto apply Report an error

  “When you deploy a new minor version of your connected system, Appian automatically starts using the new version in all connected system and integration objects.”

• Versioning major packaging rule Report an error

  “Different major versions must be packaged in the same appian-plugin.xml, but packaging two connected system templates with the same name and same major version together will result in an error when the plug-in is loaded.”

• Versioning major change examples Report an error

  “Adding a new required field (existing connected system or integration objects won't have this field populated)”

• Versioning minor change examples Report an error

  “Use minor versions when you add functionality that is compatible with prior versions of your plug-in.”

• Versioning patch change examples Report an error

  “Use patch versions when you fix bugs or update non-functionality that is compatible with prior versions of your plug-in.”

• Versioning backward compatibility Report an error

  “The promise of backward compatibility is core to the Appian platform, and therefore, it is important for your connected system to use the different versioning options provided.”

6 facts read from this page are not shown because they could not be confirmed on the page as captured.

Scores citing this record

• The Data Protection Officer Process design, forms & approvals
• The Data Protection Officer Process design, forms & approvals
• The Head of IT Process design, forms & approvals
• The Integration Engineer Process design, forms & approvals
• The Integration Engineer Process design, forms & approvals
• The Operations Analyst Process design, forms & approvals
• The Operations Analyst Process design, forms & approvals
• The Skeptic Process design, forms & approvals