Approver can't Modify order

[RSU]

Is there any known reason for approver not being able to Modify user order placed?

Approval works otherwise. I've ensured there is no item in Approver's own cart. Modify feature works in one store (uStore 25) and doesn't work in another. Settings generally done are intact.

The store in question has different user groups. In case approver is a member of other user groups also, can it impact on Modify ability?

Any thoughts will be welcome...

[couch]

If you have double-checked all the settings between the store that works and the one that doesn't - I can only suggest:

* check the stores are using the same theme. From memory the buttons to approve/reject/modify the order are in the theme and perhaps a theme which is not updated is not showing the buttons.

* check the uStore logs for any useful information about why it is not shown

* contact XMPie support for more help.

[RSU]

I'll try that and get back. Thanks for the feedback.

[RS User2]

As checked looks like NG theme modification will be needed, there's no access to capture events on approval page programmatically apparently due to NG theme imposed limitations, if I'm correct.

Any other workaround that could be of help?

Thanks.

--
You received this message because you are subscribed to a topic in the Google Groups "XMPie Interest Group" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/xmpie-users/xyNSmC29qug/unsubscribe.
To unsubscribe from this group and all its topics, send an email to xmpie-users...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/xmpie-users/f096dbd4-7bb1-4908-a165-9e2720530897n%40googlegroups.com.

[Wayne]

Not sure about this - the Modify button is a legacy page which takes the approver back to their cart to edit the Item.

Can you send a pic of the page with the modify button not working

Regards,

Wayne

[RS User2]

This is what it looks like, without Modify button, as visible to approver:

In NG Theme it has the button though:

.

The button element exists on page but its not visible to clicked.

Now when I try modifying theme, it build but upon opening localhost it errors (being not too experienced in react)

Issue with ng theme local environment setup

Not sure if this page is even available to edit in the theme as you mentioned its legacy, thanks.

To view this discussion visit https://groups.google.com/d/msgid/xmpie-users/a9699139-9d3d-40aa-8135-f8005f38113dn%40googlegroups.com.

[RS User2]

 

The react app ran with an issue. Firstly error: “Error: error:0308010C:digital envelope routines::unsupported” statedly arises due to Node version 17 or later incompatibility with OpenSSL. The work around “--openssl-legacy-provider” works only when I downgrade to Node  v20.18.3

to v16.17.0. It runs the application in the browser.

 

However as stated above I referred to another group post to remove sass from package.json and install globally. Consequently its erroring out on it and the UI shown is broken:

 

Cannot find module 'sass'

 

ModuleBuildError: Module build failed (from ./node_modules/@zeit/next-css/node_modules/mini-css-extract-plugin/dist/loader.js):

ModuleError: Module Error (from ./node_modules/sass-loader/dist/cjs.js):

Cannot find module 'sass'

 

I see about sass:

https://www.npmjs.com/package/node-sass

Node Sass is no longer supported. Please use `sass` or `sass-embedded` instead.

 

After the theme is properly working I may be able to fix Modify approvals.

[Wayne]

Many thanks for the pics - yes the Modify button is from the OrderDetails.aspx page and it is legacy.

So creating an NG Theme will not help.

The button is essentially enabled by checking the SQL Function fn_ACL_IsAccessAllowed to see if they have modify access.

I would check this function against the user and ensure the function fn_ACL_IsAccessAllowed is returning 1

You can use

  SELECT [dbo].[fn_ACL_IsAccessAllowed] (<<approver userid>>, 27, 0)

If not I would suggest rechecking and adding the correct approval permissions on the group as the ACL data may not have been saved correctly for that UserGroup.

Trying to override the setting in NG when the underlying permission is not set - is likely to cause further problems.

Also are you sure you are trying to develop against AquaBlue for uStore 25

Regards

Wayne