back

Public forms

To configure public access to a form any community can now publish a public link where we can configure to create a new instance or new subprofile for the new joinee. Configuration section is placed in the community config and it looks like...

(As planned, a config workflow needs to generate this section via worker execution)

To create new subprofile inside application adoption scope

"tokenAccess": {
    "TOKEN101": {
      "cardinality": "single/multiple",   //default is multiple. It validates from user favourite as of now
      "application": {           //SCOPE   application/profile/subprofile, examples below
        "applicationId": "AAAAAA",
        "create": {
          "category": {         //ACTION    category/newinstance, examples below
            "id": "XXXXXX",
            "processId": "cccc"  //ID of primary process of sub profile
          }
        }
      }
    }
  }

To create new subprofile inside profile scope

"tokenAccess": {
    "TOKEN101": {
      "cardinality": "single/multiple",
      "profile": {
        "profileId": "BBBBBBBBB",
        "create": {
          "category": {
            "id": "XXXXXX",
            "processId": "cccc"
          }
        }
      }
    }
  }

To create NEW INSTANCE process inside application scope

"tokenAccess": {
    "TOKEN101": {
      "cardinality": "single/multiple",
      "application": {
        "applicationId": "AAAAAA",
        "create": {
          "newinstance": {
            "processId": "YYYYYYYYY"
          }
        }
      }
    }
  }

To create NEW INSTANCE process inside profile scope

"tokenAccess": {
    "TOKEN101": {
      "cardinality": "single/multiple",
      "profile": {
        "profileId": "AAAAAA",
        "create": {
          "newinstance": {
            "processId": "YYYYYYYYY"
          }
        }
      }
    }
  }

To create NEW INSTANCE process inside subprofile scope

"tokenAccess": {
    "TOKEN101": {
      "cardinality": "single/multiple",
      "subprofile": {
        "profileId": "AAAAAA",
         "subprofileId": "AAAAAA",
        "create": {
          "newinstance": {
            "processId": "YYYYYYYYY"
          }
        }
      }
    }
  }