V7 Conditions Not Working and other issues

bucobill

Hello,

Has anyone else who has updated to version 7 had the following issues?

Condition: (if left blank operation is always applicable)
Calendar Showing <span class- "aw-line- image> instead of label
Reference Item - More options - Summary Shows - Total:<<Sum Account.Balance>> in the displayed form.Forms that had Save and Cancel on the bottom now have no action buttons
Visual Perspective- Query- Invisible When Not working the same for all users

Condition: We have conditions in a form where certain processes or queries are run only when certain conditions are met for instance if LoggedInManager.AccessLevel='Manager' and LoggedInManager.ChargeRate='20' if these are met display this query, but if the manager ChargeRate were equal to 19 then it shouldn't be displayed under version 6 this worked fine.

Calendar: Worked in version 6 but 7 has issue listed above

Reference Item: Worked in version 6 but in 7 is showing the complete rule used to create a summary of an attribute where we are trying to get a total.

Visual Perspective- Invisible When: This is working for some users such as staff without issue but under Manager everything is showing. Worked previously in version 6.

If anyone could help it would be appreciated.

bucobill

Figured out on Calendar the issue is in the Process rules. The rule changed the FOR EACH and WITH to for each and with. I changed these and it appears to work. It did it in each of the processes.

bucobill

OK. So on the issue of making something accessible under Panel Operations - Applicability to make something accessible by a rule what I have found is that each "Name" must be unique where as in previous versions you could have all "Names" be the same and the query or process be unique. In this one each has to be unique, two days to figure this out , great :? 🙁

tford

Do you mean all names within 1 VP ... all names within 1 VP tab .. or something else?

aware_support

"Calendar Showing <span class- "aw-line- image> instead of label"

This was fixed in one of the recent builds. Please get the latest one.