[DOCU-1953] Make the chapter on Groovy module's Rescue app even more helpful Created: 30/Aug/19  Updated: 16/Sep/19  Resolved: 10/Sep/19

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Neutral
Reporter: Maxime Michel Assignee: Martin Drápela
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File cumulus-filter.png    

 Description   

I recently used this guide to bring an instance back up, and the step by step procedure worked very smoothly, I was really happy about that. However, I did run into difficulties and would like to suggest a couple of improvements so that as much information as possible is available for future emergency situations (for me or others).

Make session.save() bold or red

Tweaking a node and leaving it there unchanged is a frequent source of wasted time during development. Forgetting to save the session is even more likely to happen under stress. I would suggest highlighting it one way or another.

Describe how to tweak a property

The steps describe how to remove a stray node, but a more realistic situation would be to tweak a property, for instance: set a problematic filter's enabled property to false. Under stress and without any IDE help, I struggled to find the syntax to read a property's value: node.getProperty('enabled').getString().

node.setProperty('property', 'newValue') was a bit more easy to figure out, but it would have been even easier if they both had been on the page.


Generated at Mon Feb 12 01:22:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.