Automate

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com

Using VK34, attempting to create a Transaction script to update Customer Item pricing.  If the new price being created overlaps an existing price condition based on Validity Dates, then a pop-up screen is to appears to confirm the new price.   Problem is the pop-up screen is a bit erratic and causing error conditions to appear in the script log even when the data is actually saved.

 Found a support entry indicating pop-ups after a save operation should not be relied upon using the "Skip  Screen if Not Present" property.   Instead, it suggested placing the pop-up in a condition statement rather than using the property.   Here is the section of my script:

 Any suggestions for what such a condition would look like?

 Thanks, and appreciate your input.

 Dave Leon

KIS Technologies Inc.

Mobile:  (713) 201-0041  

eMail: DaveLeon@Hotmail.com