Appian Senior Developer
Integrations - HTTP Status code 401 - ✔✔Unauthorised Access
Integrations - HTTP STatus Code 404 - ✔✔Not found
Integrations - Authendication - Two ways to configure authendication - ✔✔1. Connected
Systems
2. Secure credentials Store
Integrations-Authendication - Where can Secure Credentials Store configured - ✔✔Appian
Admin Console
Integrations-Authendication - Expression function - Access Secure Credentials Store -
✔✔a!scsField
Integrations - Node used to call integrations from process model - ✔✔Call Integration
Integration - Using in Expression - ✔✔Using an expression only works for querying data in an
integration.
Integration - Query Data - ✔✔Only works with Expression
Integration - Modifies Data - ✔✔1. Works with "Call Integration" smart service in process
model
2. Submit from Interface
Integration - Modifies data - Additional parameters added to integration by default - ✔✔1.
OnSuccess
,2. OnError
Integration - Common methods of performing integration over HTTP - ✔✔1. REST - "Call
Integration"
2. SOAP(WSDL) - "Call Webservice"
Three Anti Patterns to avoid - ✔✔1. Custom Task Management
2. Custom User Interfaces (Third party UX)
3. Avoid Data only applications
(Extracting, Transforming and Loading)
Appian Task Plugins - ✔✔1. Task Reassignments
Allow users to reassign multiple active tasks
2. Task Functions
Allow developers to retrieve most task details and attributes by using a set of functions with
Task ID as input.
3. Task Management Smart Services
Contains smart services to manipulating tasks in-process and custom functions for getting task
metadata.
Data-only processes can slow the system. Particularly if they are running during business hours
when most users are acitve - ✔✔Yes, True.
Mitigation strategies to reduce the impact of data-only processes on performance for other
active users. - ✔✔1. Data management (Delete the process instance immediately after the
process completed)
2. Make process variables "hidden" to limit data replication for reports
3. Avoid load bulk data to system during business hours
4. Do not store the data to process variables
, Record Centric Design - Benefits - ✔✔1. Faster to build
2. Easier to maintain
3. Incorporate simpler and short-lived processes
4. Make better use of system resources
Record Centric Design - Steps - ✔✔- Start with key building blocks of data in a relational
database
- Use an entity-backed record type that allows users to list, search, filter, and drill down into
data in that entity.
- Attach an action to allow users to create new records
- Use related actions to enable record update and status changes
- Repeat this process for each key resource that needs to be managed.
Query Anti Patterns to avoid - ✔✔1. Should not keep "batchSize" as -1. (This will try to fetch
all data)
2. unsorted query results (Keep primary key as the sort id)
3. "ends with" filtering conditions.
4. using 50 or more operators using "in" operations, will result very slow query.
When Query will break with error - ✔✔Query breaks if the data returned is > 1MB or takes
>10 Seconds
DB Design practices to follow - ✔✔1. Implement locking mechanism for DB updated to avoid
race conditions
2. Load test your applications with roughly three times the anticipated first year's worth of
data.
3. Avoid designing queries that are unbounded or slow
Integrations - HTTP Status code 401 - ✔✔Unauthorised Access
Integrations - HTTP STatus Code 404 - ✔✔Not found
Integrations - Authendication - Two ways to configure authendication - ✔✔1. Connected
Systems
2. Secure credentials Store
Integrations-Authendication - Where can Secure Credentials Store configured - ✔✔Appian
Admin Console
Integrations-Authendication - Expression function - Access Secure Credentials Store -
✔✔a!scsField
Integrations - Node used to call integrations from process model - ✔✔Call Integration
Integration - Using in Expression - ✔✔Using an expression only works for querying data in an
integration.
Integration - Query Data - ✔✔Only works with Expression
Integration - Modifies Data - ✔✔1. Works with "Call Integration" smart service in process
model
2. Submit from Interface
Integration - Modifies data - Additional parameters added to integration by default - ✔✔1.
OnSuccess
,2. OnError
Integration - Common methods of performing integration over HTTP - ✔✔1. REST - "Call
Integration"
2. SOAP(WSDL) - "Call Webservice"
Three Anti Patterns to avoid - ✔✔1. Custom Task Management
2. Custom User Interfaces (Third party UX)
3. Avoid Data only applications
(Extracting, Transforming and Loading)
Appian Task Plugins - ✔✔1. Task Reassignments
Allow users to reassign multiple active tasks
2. Task Functions
Allow developers to retrieve most task details and attributes by using a set of functions with
Task ID as input.
3. Task Management Smart Services
Contains smart services to manipulating tasks in-process and custom functions for getting task
metadata.
Data-only processes can slow the system. Particularly if they are running during business hours
when most users are acitve - ✔✔Yes, True.
Mitigation strategies to reduce the impact of data-only processes on performance for other
active users. - ✔✔1. Data management (Delete the process instance immediately after the
process completed)
2. Make process variables "hidden" to limit data replication for reports
3. Avoid load bulk data to system during business hours
4. Do not store the data to process variables
, Record Centric Design - Benefits - ✔✔1. Faster to build
2. Easier to maintain
3. Incorporate simpler and short-lived processes
4. Make better use of system resources
Record Centric Design - Steps - ✔✔- Start with key building blocks of data in a relational
database
- Use an entity-backed record type that allows users to list, search, filter, and drill down into
data in that entity.
- Attach an action to allow users to create new records
- Use related actions to enable record update and status changes
- Repeat this process for each key resource that needs to be managed.
Query Anti Patterns to avoid - ✔✔1. Should not keep "batchSize" as -1. (This will try to fetch
all data)
2. unsorted query results (Keep primary key as the sort id)
3. "ends with" filtering conditions.
4. using 50 or more operators using "in" operations, will result very slow query.
When Query will break with error - ✔✔Query breaks if the data returned is > 1MB or takes
>10 Seconds
DB Design practices to follow - ✔✔1. Implement locking mechanism for DB updated to avoid
race conditions
2. Load test your applications with roughly three times the anticipated first year's worth of
data.
3. Avoid designing queries that are unbounded or slow
