1) When should an input and output of the node be used ?
A) Input of node is used when one needs to pass the input to the node for its functionality. The input can also be defined when the ac has to used in the output of the node for any manipulation.
Output of the node is either used to take the results of the node's functionality or to customised our own outputs by manipulating the values
2) What is the purpose of using the Stored Values in write to data store entity node's output ?
A) It is to retrive the output of the data stored in the DB along with pk value when pk is auto generated
3) When a process with a active task is paused, will the task be available to the user to perform ?
A) No. An error will be shown to user when the task is opened
4) Will timer node execute when the instance is paused ?
A) Yes
5) When should local variables be used ?
A) Local variables are used when the scope is within the interface/rule and the value need not go outside that object. They are also used to define the repeitive piece of code/function/rule.
6) What are the different ways to refresh a local variables ?
A) Local variables can be refreshed on the following ways:
1. refreshAlways: When true, the value of this local variable will be refreshed after each user interaction and each interval refresh.
2. refreshInterval: How often the variable value gets refreshed in minutes. When null, the variable will not be refreshed on an interval. Valid values include 0.5, 1, 2, 3, 4, 5, 10, 30, 60.
3. refreshOnReferencedVarChange: When true, the value of this local variable will be refreshed each time the value of any variable it references within the value parameter is updated. Default is true.
4. refreshOnVarChange: Refreshes the value of the local variable each time any of these specific variables change. This allows you to refresh the value when a variable that is not referenced within the value parameter is updated.
5. refreshAfter: Refreshes the value of the local variable after a record action, such as a related action or a record list action configured within a record type, completes from a dialog window within the Record Action Component. Instead of requiring the entire page to reload, this parameter allows you to refresh a local variable value on an interface after a record action completes. Valid values include RECORD_ACTION.
7) Why shouldnt a interface have more than 500 lines of code ?
A) How to reduce the number of lines of code? More than 500 lines of code leads to binding issues and this can be solved using Modular coding
8) What is purpose of Set as Default test cases ?
A) It will set the values given to an ri in the interface as default. Whenever the interface is opened these values are assigned to the ri. This makes the testing of interfaces expecially readonly interfaces easier
9) What is a MNI and its best practices ?
A) Multiple Node instance is to create multiple instance of a node. This is done when the functionality of the node is to be repeated for various inputs. The best practice is do a null check of the variable before the MNI and if the variable has more than 1000 values, it is recommened to do batch process (Split the input to MNI into smaller values and send to MNI)
10) What are the different types of records created in Appian ?
A)
1. Entity Backed Records;
2. Service/Expression Backed Records;
3. Process Backed Records
11) What is a data sync and when should I use it ?
A) When data sync is enabled, you are caching your source data in Appian. With a cache of your data, this means Appian will only have to execute queries from the cached data instead of the external source whenever you view or interact with the record data. Refer here on when to use data sync.
12) When should default filters and user filters be used ?
A) Default filters are used when the filter has to be applied to source while retriving the data for the record type
User filters are the filters applied by the user once the record type list is displayed.
13) How many additional views can be added to a record type ?
A) Total 20 along with Summary view
14) Sites In Appian ?
A) Site is nothing but end user portal ,and it is customized portal. Here the advantage of Site compare to Tempo is…
We can customize the tabs and we can maintain the security for each tab .
There is no News tab in the Site.
Compare to Tempo there is no fixed tabs like records, reports , actions, tasks and News.
In site the inputs are Records, Reports and Actions. If you want to configure Interface in site we have to create interface and configure in reports, That way we can configure.
But in New version 21.2 we can directly configure User interface into the Site. So now the inputs of Site are Records, Reports ,Actions and User Interface.
Also we can keep it customized icon for each tab and we can change the button style and Border style.
15) How do you maintain Data management of Process Model ?
A) Data management of process model is nothing but Archive and deletion of Process Instances.
Process instances are nothing but process model running stages like completion,reject,cancel,error..etc which is present in monitoring tab in development environment.
In process model data can manage and customize by default we can set 0 to 999 days.
There is 2 ways to data management in Process model.
Archive:- By Default in apian can archive the data up to 7 days. If you want to change we can customize. Here the meaning is if we archive the process instance data it will store some were in the appian and we can retrieve the data.
Delete:- This is also same as like a archive but the difference complete process instance has been deleted, not possible to retrieve the process instances.
16) Best Practices to Create Process Model ?
A) Best practices…….
Security maintenance as per assignment.
While Creation of process model proper naming convention for process model and Process display name.
Use Activity Chaining wherever required and avoid to use unnecessarily.
Always enable activity chain from Start node.
Use sub process and Start process smart services wherever required to reduce the flow length.
Use Swim lanes to divide and distribute the flow.
Configure Data management.
Use alerts.
Use Escalations and Exceptions.
Use mail configuration to rectify errors.
Avoid to use MNI(multiple node instances).
Naming convention for each node as per the functionality.
Use Paragraph field to understand the process for new Employee.
17) Gate ways in Process Model ?
A) Gate ways in the process model is nothing but OR, XOR, AND and Complex gateways.
18) What are smart Services Used in Process model ?
A) Explain Any 10 Smart services which you know in the process model.
Like user input task, Write to data store Entity , Script task ,Gate ways, Send Email , Write to multiple data store entity….etc.
19) What is foreach() function ?
A) foreach() function is nothing but looping function.
Syntax:- a!foreach(items,expression)
Items:- Number of values or parameters to iterate.
Expression:- Expression to iterate each values.
Try to give one Example.
20) How many ways to create CDT ?
A) There are 5 ways to create CDT.
Create From Scratch:- To Create CDT from Scratch.
Create From Table or View:- to Create CDT from existing table or View in the Data Base.
Create From Duplicate:- To Create from Existing CDT in the Application or External application.
Create From XSD:- To Create Fro XML Schema Document.
Create From Web Services:- to Create from third party web Services.
21) Difference between Entity Backed, Process backed and Expression Backed records ?
A) There are 3 types of records in appian…
1.Entity backed record:-
Record created with Database Entity called Entity Backed records. Data Source is Database Entity. Entity may be database table or view.
2. Process Backed Records:-
Record created to display process instances. Data source Process model.
3. Expression Backed Records:-
Record to Display data of Third party data. Ex:-Web Services.
22) What is the number of Dashboards we can configure in Records ?
A) Best Practice is 30 but we can configure n number dashboards.
23) Difference between Action and Related Action ?
A)
Actions:- Action is nothing but fresh flow it means new user can enter the data into the database. Here for configuration of Actions into the tempo we have to navigation bar in the top right corner and click on Application actions and configure the respective process model. To Start a action there is parameter required.
Related Actions:- related Actions are nothing but to update existing data in the database we can go for related actions. Which is configured in the Records. To Start a process compulsorily a parameter is required.
24) Can we configure user interface in site ?
A) No
In new release version 21.2 we can configure user interface in Site.
But in previous version if we want to configure user input task into site first we have tempo report through interface, than that report we can configure into site.
25) What are different inputs we have for constant ?
A) Text, Number(Integer), Number(Decimal), user, Expression rule, Record, report, Folder, Group, Document, Document/Folder,Data Store Entity,Boolean..etc
26) How can you get DDL script of tables from Appian ?
A) In data store entity we have button call DDL Script there we can download.
27) I have 100 rows in a table and I want to display in interface and need to provide edit functionality for the user, so which grid id better to use ? Explain.
A) We should go for editable grid because it editable format like we can add or delete the column and we can change the row data . Here we can display data in readonly format also.
But why we are not prefer read only grid means there is no editable .
28) Difference between where(),index(),wherecontains() and contains() functions ?
A) Please go through on Appian documentation and Explain about Syntax.
29) Difference between Default filter and User Filter ?
A)
Default Filter : The filter will apply list of variants in the table and display the data.
User Filter: The filter will apply particular column and display the data.
30) I need Employee first name column from table where Employee firstname=Kumar and workLocation=Pune, Explain code in Query Entity ?
Answer:- a!queryentitty(
entity:cons!getemployee_details,
query:a!query(
paginginfo:a!paginginfo(startindex:,batchsize: -1)
selection:{
a!queryselection(field:”firstname”),
a!queryselection(field:”workLocation”)
}
)
)
No comments:
Post a Comment