Kinetic BPM Maintenance - Custom Code Editor = 7 lines?

When I try to edit a Custom Code block in a data directive, the editor in Kinetic browser 2025.1.11 will only show 7 lines of code. There doesn’t seem to be a way to get a full-screen editor, or am I missing something?

Try this…

First, click and drag the bottom pain divider down to give yourself more space on the page. (circled in green below).

Then… Double-click on the upper divider, on the item you circled in your picture… then try to drag it down.

1 Like

Thanks but already tried that. Even with the bottom pane pushed almost off the bottom of the screen, the editor pane will not expand beyond 7 lines. (This is in plain ol’ Google Chrome.)

1 Like

Also using chrome.

I was able to get up to 35 lines by doing this:

1 Like

Ok, that makes no sense - why is your Chrome better than my Chrome!? :slight_smile:

2 Likes

I still don’t know why I have to double-click it in order for it to work. After doing that, I can move it up and down as it was intended. :thinking:

I agree, doesn’t make much sense why it works for me and not you.

I’m also using 2025.1.11

Just tried it in Edge browser… I didn’t have to double-click… if I drag the bottom pain down, the upper pain automatically got larger to take up the space.

Interesting.

Doh, I completely missed the ‘double-click’. Yea, that works now, although I can only get about 26 lines to show (seems to depend on screen resolution).

Still, this seems an incredibly weak replacement for a full-screen editor.

5 Likes

I find it completely unusable. I want bpms to be included in power tools.

7 Likes

As an aside, I also notice that if I add or remove an assembly reference, the syntax checker does not recognize the change. Saving the BPM makes no difference. I have to close the BPM completely and edit it again for the change to be recognized.

4 Likes

That do you mean by does not recognize? What exactly is not working?

If I am editing a custom code object in Kinetic BPM Studio, and I add new code that requires an additional assembly reference, then I can add the assembly reference with the 3-dot menu and ‘Save’ on that slideout. But if I now hit ‘Check Syntax’ I still get the same errors as if I had never added the assembly.

Similar thing happens if remove an assembly that the code requires, then do ‘Check Syntax’: it will says ‘Syntax OK’ even though the assembly reference is no longer present.

Even worse, going in and out of a BPM seems to confuse the app. Here is the same BPM at the same time being shown in Classic and Kinetic. In Classic you see the assembly references; in Kinetic, they don’t even appear (at right), and yet ‘Check Syntax’ says its all good, so behind the scenes the Kinetic app “knows” the assemblies are present:

1 Like

If I close the BPM Studio app tab in the browser and open it from the menu again, then magically the assembly references now show:

2 Likes

So steps are: 1. Open References, Add one, close.
2. Open again, it is empty? or not?

It’s not great at all and I would like to see Classic’s version in Power Tools until Kinetic can get a better version created. But doesn’t look like we’ll get that option.

3 Likes

Issue 1: Add/delete of assemblies not recognized by syntax checker:

  • Open references > Add reference > Save (at bottom of slideout) > Close
  • ‘Check Syntax’ button will not recognize newly added assembly.

Issue 2: Assemblies do not appear in References slideout:

  • Not exactly clear…it may require more clicking around than below:
    • Open BPM > open custom code block
    • Click on BPM Studio in breadcrumb
    • Reopen BPM > open custom code block > References > Assemblies are missing
2 Likes

No reason why we shouldn’t - power tools is literally just a menu with pointers to a limited selection of classic programs. It would be trivial to include method directives maintenance and data directives maintenance.

5 Likes

Agreed but the powers that be don’t seem to be willing to throw us a bone even though it’s easy as just keeping a few more DLLs around a bit longer.

1 Like

I don’t see issue 1 in the new version, but I see the second - something wrong happens when you go through breadcrump back to the same directive.
Here is PRB for the reference: PRB0305220

For now, if you want just to close editor without clicking on save you can use X symbol in the top right corner.

2 Likes

There is an idea out there for a browser full screen code editor

1 Like