Extension values did not get applied to new Environment/Atom

Document created by mike_aronson Employee on Jan 13, 2014
Version 1Show Document
  • View in full screen mode
A new environment and atom/molecule/cloud  was created, and existing processes were deployed to it, but the extension values were not applied automatically.
or
An atom/molecule/cloud was newly attached to an existing environment, but the password values were not applied to the new atom/molecule/cloud automatically.
When a new environment and atom/molecule/cloud is created or processes are deployed to a different environment/atom for the first time, the extensions will default to "Use default".

You will need to go to Manage -> Environment Extensions for the new atom/environment to set the values the first time right after the deployment.

Passwords need to be re-entered after a new or different atom, molecule or cloud is newly attached to an existing environment where processes were already deployed and extensions were already supplied before.

Attachments

    Outcomes