Overview
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.
Properties
-
Category: Document Management
-
Icon:
-
Assignment Options: Attended/Unattended
Configuration options
This section contains tab configuration details specific to this smart service. For more information about common configurations see the Process Node Properties page.
Data tab
This tab displays all the Node Inputs and Node Outputs for the Service Node. You can add additional inputs and outputs, if needed.
Node inputs
The default inputs are:
| Input | Type | Required | Multiple |
|---|---|---|---|
| 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.
Node outputs
To retain the ID of the KC for use elsewhere in the Process Model:
- Click the Outputs property sheet.
- Select The created knowledge center. The Result Properties are displayed.
- Create a Process Variable or select an existing PV (with a Knowledge Center data type) from the Target list.
a!createKnowledgeCenter()
The Create Knowledge Center smart service is available as an expression function that can be executed inside a saveInto on a Interface Component or as part of a Web API.
Syntax
a!createKnowledgeCenter( name, description, onSuccess, onError )
Parameters
| Keyword | Type | Description |
|---|---|---|
|
|
Text |
|
|
|
Text |
The description of the new Knowledge Center. |
|
|
Any Type |
A list of saves or an HTTP response to execute after the smart service executes successfully. Created with |
|
|
Any Type |
A list of saves or an HTTP response to execute when the smart service does not execute successfully. Created with |
Feature compatibility
The table below lists this smart service function's compatibility with various features in Appian.| Feature | Compatibility | Note |
|---|---|---|
| Portals | Partially compatible | Can be used with Appian Portals if it is connected using an integration and web API. |
| Offline Mobile | Incompatible | |
| Sync-Time Custom Record Fields | Incompatible | |
| Real-Time Custom Record Fields | Incompatible | Custom record fields that evaluate in real time must be configured using one or more Custom Field functions. |
| Process Reports | Incompatible | Cannot be used to configure a process report. |
| Process Events | Incompatible | Cannot be used to configure a process event node, such as a start event or timer event. |
Old versions
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 |
|---|---|
| a!createKnowledgeCenter_17r4 | The securityLevel has been removed in the Appian 18.1 release. Knowledge center security is managed completely by normal object security. |
To use the latest version of the smart service node:
- Drag in a new Create Knowledge Center Smart Service node from the palette, and place it on the same connector as the current node.
- Configure the new node with settings matching your current, older node.
- Delete the old Create Knowledge Center Smart Service node.
To learn more about how Appian handles this kind of versioning, see the Function and Component Versions page.