A knowledge center is a second-level container in Appian Document Management (below Communities). All folders and files are stored in knowledge centers. By creating knowledge centers and granting access to other users, you can share files and collaborate on them, either within a process, or through a portal page.
The Create KC smart service node allows you to create a knowledge center and configure its security from a process.
Category: Document Management
Assignment Options: Attended/Unattended
This section contains tab configuration details specific to this smart service. For more information about common configurations see the Process Node Properties page.
This tab displays all the Node Inputs and Node Outputs for the Service Node. You can add additional inputs and outputs, if needed. The default inputs are:
|Knowledge Center Name||Text||Yes||No|
|Knowledge Center Description||Text||No||No|
If the node is run without being assigned to a user (or a group) you must specify values for each of the Node Inputs listed in the table above. You can either manually enter data into the text-field, or a value can be generated using the using the Expression Editor. When using the Expression Editor, you can reference and modify Process Variables, rules, constants, and other data. The expressions then specify your Node Input values.
If the node is assigned, the Node Input values are collected from a form.
To retain the ID of the KC for use elsewhere in the Process Model:
a!createKnowledgeCenter(name, description, onSuccess, onError)
a!httpResponse(). The following function variable is available when configuring this input:
There are older versions of this Smart Service. You can identify older versions by looking at the name to see if there is a version suffix. If you are using an old version, be sure to refer to the corresponding documentation from the list below.
|Old Versions||Reason for Update|
The securityLevel has been removed in the Appian 18.1 release. Knowledge center security is managed completely by normal object security.
To learn more about how Appian handles this kind of versioning, see the Function and Component Versions page.
On This Page