Jump to content
igriesd

Web Scripts Error - Known Issue 1109583

Recommended Posts

Hey everyone!

My name is Ian, I work on the Product team at Connectwise. I'm (obviously) not active on the forums, but you can find me in slack under igriesdorn if you'd like to chat.

Wanted to talk about KI 11109583, which is the /Automate web throwing an error when a limited user clicks on the Scripts button.

We identified an issue where if a partner has rows in their lt_scripts table that have blank values for Permissions, and EditPermissions, it is what is causing this error for the non super admin accounts.

Running the following query will identify any scripts that are both 1) Blank, and/or 2) Not properly terminated:

SELECT *
FROM lt_scripts
WHERE Permission = '' OR Permission NOT LIKE '%,%'

Partners can then go to those scripts in the product, navigate to the Permissions tab, and set user class permissions to limit as they wish, then save the script. If they add a user class to a blank window, and remove it, it will add in "0," to the two columns in the database. While manual database manipulation is not recommended by me, if you want, you can update the values manually to 0,

We have a 20 count of partners on this KI right now, and it's mostly MSPGeek (had to delete and correct that name 😅) on the list, so I thought it would be good to reach out to you all on the forums and through Slack to see if we can get the information propagated out in the community.

We will be putting in a fix in the product that will prevent your /Automate web page's script button from throwing the error.

Thanks,

Ian Griesdorn

 

  • Like 1
  • Thanks 3

Share this post


Link to post
Share on other sites

Thanks for this Ian. Identifying things like this and releasing workarounds to the community make all the difference rather than waiting months for it to come through in a patch, so I just wanted to take the time to say thanks and if more things like this can be done for known issues, it will change the perception of 'ticket logged, see something in a few months hopefully'. 

So once again, thanks. Very much appreciated. 

  • Like 3

Share this post


Link to post
Share on other sites

THANKS!! Just confirmed this worked for us on 12.12. Upgrading to 2019.2 tonight so hoping this fix 'sticks' for us.

  • Like 1

Share this post


Link to post
Share on other sites

Post-upgrade we're still looking good on this.

I fully echo what @Jacobsa said above. I really hope this is a sign of 'more to come' with CW engaging with this community like this to help provide workarounds and solutions. It's greatly appreciated.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×