BPM Automation Studio Widget down - Only fixing for 2025.1.16

Kinetic ERP
1

FYI. In case you’re using the Automation Studio widget and seeing issues in your recipes. Note the last line - once fixed it will only work for 2025.1.16. Bad news if you’re on any other supported version of Kinetic.

image
image1268×305 14.4 KB

Actual Email

BPM Automation Studio Widget down

The BPM Automation Studio widget is currently undergoing unplanned maintenance. We will notify you as soon as the work is completed and fully tested.

We understand the importance of this service to your business and sincerely apologize for any inconvenience this may cause. Please note that this maintenance only affects the Automation Studio widget within BPM. All other Automation Studio functionalities remain fully operational.

Once the service is back, it will only work for Kinetic version 2025.1.16 and onwards. This is due to the security enhancements for the underlying APIs which communicates with Kinetic BPM.

Thank you for your patience and understanding.

5 Likes
2

What the heck! So I’m just out of luck?

2 Likes
3

I’m asking the same thing! How can this be a solution or acceptable?!

2 Likes
4

If this is true, I will be seriously considering dropping Automation Studio. You can’t just do that to customers in production. We can’t just upgrade to a major version overnight.

3 Likes
5

We would be likely forced to drop it and look for another solution. I don’t know how you tell customers on supported version “sorry, you can’t use this anymore. Upgrade”.

3 Likes
6

Wow, that’s totally not acceptable in my book.

Fire Oops GIF

7

AT this point I’d be demanding to get base Workato so you can roll your own Epicor connector.

2 Likes
8

This looks to only affect the BPM widget to call an automation studio recipe from a BPM which uses the API behind the scenes.

This is unique to Automation Studio and not a feature you would get in Workato direct whithout creating your own function / bpm to compose and send the REST call.

Don’t get me wrong I still thing this is atrocious to drop on people..

1 Like
9

Correct. But, if you have Automation Studio and are calling it from a BPM. And now are told you can’t. That’s a big problem.

Yes, you could call it from a function. But that means redoing your BPMs and writing functions to do what’s built in.

1 Like
10

110% agree.

Just want to make it clear.

It will make me rethink using the widget at all in future… it was fussy to begin with.

1 Like
11

Ok, sure. But why can’t we get an update on all supported versions. Where’s my 10% going?

image
image666×327 14 KB

2 Likes
12

Is this the kind of improvements the 10% increase is paying for?

3 Likes
13

This Is Fine GIF

1 Like
14

The fact it is unplanned maintenance must mean that a serious security flaw must have been found…..

15

Still no excuse to just drop supported versions of Epicor

1 Like
16

I’m guessing. But that doesn’t mean you can’t fix it in all supported versions.

2 Likes
17

2025.1 is so arbitrary. Let’s hope it’s just an oversight and they will be looking at all other supported versions soon.

4 Likes
18

Hope so. To just cut it off in the middle of the day with no notice and pick a random 25.1 version is so disruptive.

2 Likes
19

How does a widget even go down?? Guessing they found a vulnerability of some kind and then blocked it on the automation studio side?

@Olga do you know what’s going on?

20

Afaik Workato changed authentication process, widget had to be updated.

Ask support if Hotfix available for your version

3 Likes