Skip to main content
Nintex Community Menu Bar

Best Practices for Automation

  • August 29, 2019
  • 0 replies
  • 65 views
  • Translate

Lyubomir
Nintex Employee
Forum|alt.badge.img+3

Recording rules:

• 100%DPI.

• When using visual approach make sure to use commonly DPIs used (By users) resolution 

• If the screen sizes are not the same make note and plan accordingly 

• Don’t ever define a web browser as an application.

Windows rules: 

• Try to be as specific as possible regarding window deduction.

• Don’t put a long wait time for finding a window as this will keep the bot ideal until that period is over.

• If you use a visual action in your flow don’t add the visual command to your window tab.

Advanced commands:

• Always at the end of the step.

• There are ADC which you can’t use in a ADC step (Because they require a visual step)

Detectable Objects:

• It must be static.

• It must be unique 

• It must at least 3 letters long.

Offsets:

• Keep the distance from the detectable object to a minimum 

• Don’t overlap your offset with your detectable object 

• Make sure that the distance between your detectable object and your offset is static.

Sensors (Attended Automation)

• Use multistep sensors

• Don’t create 2 overlapping sensors, exact same launching mechanism

• Don’t create a process within a sensor launch a sensor instead.

• Try to minimize the sensors, if possible create one sensor for multiple wizards 

• Create one application that has multiple values and utilize it throw the sensor.

Did this topic help you find an answer to your question?

0 replies

Be the first to reply!

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie Settings