APPIAN SENIOR DEVELOPER- NOTES
FOR APPIAN SENIOR DEVELOPER
CERTIFICATION WITH COMPLETE
SOLUTIONS
Successful first projects deliver results that are: - ANSWER-- Quick, with a short time-
to-impact reducing the likelihood of losing momentum
- Measurable, giving leaders the confidence to approve further projects
- Contagious, with a compelling solution triggering rapid user adoption
Prioritize Project Opportunities - ANSWER-dummy slide
Project Factors- Project complications - ANSWER-1. Extensive Data ETL
2. Complex Data Visualization Across Systems
3. Complex Data Manipulation
4. Backend Process Management
Query Anti Patterns to avoid - ANSWER-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 - ANSWER-Query breaks if the data returned is > 1MB
or takes >10 Seconds
DB Design practices to follow - ANSWER-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
In addition to entity locks table to resist concurrent table update aatempts, "Optimistic
locking" can be used to prevent the writing of stale data. using the following annotations
- ANSWER-@version and @column
Project Factors- Success factors - ANSWER-1. Automate complex business processes
2. Access data from or send data to legacy systems
3. Create unified user experience across systems
4. Deliver functionality rapidly
5. Support business processes across the organization
, 6. Enable target users to access multiple systems
7. Integrate pre-built or custom-built AI systems
8. Engage or inform multiple stakeholders across workflows
9. Perform mobile data entry (inclusive of review and approval)
Project Factors - First step to selecting a successful project - ANSWER-Finding
oppertunities to address business processes
If your project has large scsope, what is a best practice you can use that will lead to a
successfull project? - ANSWER-Break up large scope into smaller projects
Intergrations - HTTP Status code types - ANSWER-100 - Informational
200 - Success
300 - Redirect
400 - Client Side Error
500 - Server Side Error
Integrations - HTTP Status code 401 - ANSWER-Unauthorised Access
Integrations - HTTP STatus Code 404 - ANSWER-Not found
Integrations - Authendication - Two ways to configure authendication - ANSWER-1.
Connected Systems
2. Secure credentials Store
Integrations-Authendication - Where can Secure Credentials Store configured -
ANSWER-Appian Admin Console
Integrations-Authendication - Expression function - Access Secure Credentials Store -
ANSWER-a!scsField
Integrations - Node used to call integrations from process model - ANSWER-Call
Integration
Integration - Using in Expression - ANSWER-Using an expression only works for
querying data in an integration.
Integration - Query Data - ANSWER-Only works with Expression
Integration - Modifies Data - ANSWER-1. Works with "Call Integration" smart service in
process model
2. Submit from Interface
Integration - Modifies data - Additional parameters added to integration by default -
ANSWER-1. OnSuccess
2. OnError
FOR APPIAN SENIOR DEVELOPER
CERTIFICATION WITH COMPLETE
SOLUTIONS
Successful first projects deliver results that are: - ANSWER-- Quick, with a short time-
to-impact reducing the likelihood of losing momentum
- Measurable, giving leaders the confidence to approve further projects
- Contagious, with a compelling solution triggering rapid user adoption
Prioritize Project Opportunities - ANSWER-dummy slide
Project Factors- Project complications - ANSWER-1. Extensive Data ETL
2. Complex Data Visualization Across Systems
3. Complex Data Manipulation
4. Backend Process Management
Query Anti Patterns to avoid - ANSWER-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 - ANSWER-Query breaks if the data returned is > 1MB
or takes >10 Seconds
DB Design practices to follow - ANSWER-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
In addition to entity locks table to resist concurrent table update aatempts, "Optimistic
locking" can be used to prevent the writing of stale data. using the following annotations
- ANSWER-@version and @column
Project Factors- Success factors - ANSWER-1. Automate complex business processes
2. Access data from or send data to legacy systems
3. Create unified user experience across systems
4. Deliver functionality rapidly
5. Support business processes across the organization
, 6. Enable target users to access multiple systems
7. Integrate pre-built or custom-built AI systems
8. Engage or inform multiple stakeholders across workflows
9. Perform mobile data entry (inclusive of review and approval)
Project Factors - First step to selecting a successful project - ANSWER-Finding
oppertunities to address business processes
If your project has large scsope, what is a best practice you can use that will lead to a
successfull project? - ANSWER-Break up large scope into smaller projects
Intergrations - HTTP Status code types - ANSWER-100 - Informational
200 - Success
300 - Redirect
400 - Client Side Error
500 - Server Side Error
Integrations - HTTP Status code 401 - ANSWER-Unauthorised Access
Integrations - HTTP STatus Code 404 - ANSWER-Not found
Integrations - Authendication - Two ways to configure authendication - ANSWER-1.
Connected Systems
2. Secure credentials Store
Integrations-Authendication - Where can Secure Credentials Store configured -
ANSWER-Appian Admin Console
Integrations-Authendication - Expression function - Access Secure Credentials Store -
ANSWER-a!scsField
Integrations - Node used to call integrations from process model - ANSWER-Call
Integration
Integration - Using in Expression - ANSWER-Using an expression only works for
querying data in an integration.
Integration - Query Data - ANSWER-Only works with Expression
Integration - Modifies Data - ANSWER-1. Works with "Call Integration" smart service in
process model
2. Submit from Interface
Integration - Modifies data - Additional parameters added to integration by default -
ANSWER-1. OnSuccess
2. OnError
