Hello sprity,

If i understood you correctly, you want to control visibility state or togle mode of the folders tree. The handler you provided, well, is responsible for this logic.  

Here is an example of how you can do it:

Toggle mode (open if closed, close if open):
{ 
    request: 'crt.FolderTreeVisibleRequest', 
    params: { 
        folderTreeName: "FolderTree_blabla", 
        togglePanel: true 
    } 
}

Explicit visibility mode (always open or always close, regardless of current state):

{ 
    request: 'crt.FolderTreeVisibleRequest', 
    params: { 
        folderTreeName: "FolderTree_blabla", 
        visible: true  // or false to close 
    } 
}

As mentioned, this handler also saves the state to the user profile, meaning that when the page is reopened, the folder tree will be in the same state (open or closed) as it was before. If you'd prefer not to save the state in the profile, you can manually update the visibility attribute, like so:

{folder tree name}_visible => FolderTree_blabla_visible

Hope this helps! Let me know if i understood you correctly and if you have any questions let.

Yevhenii Grytsiuk,

Thank you for this Yevhenii. One of the more difficult parts of working with Freedom UI is the inability to dig into the out of the box code to see how to change the behavior. This was easy with classic, but for Freedom we have to dig through all the minified code to see if we get lucky finding what we are after. 
Until there's better documentation outlining what all the various requests are to handle, it would be great to have some sort of switch (like the IsDebug setting to enable debug mode) that just dumps all the fired requests to the console (and maybe include what object/component fired the request?) Not sure how reasonable that would be since it's likely quite a bit of stuff would show there, but might make it easier to see the requests that fire when some action is taken.

Ryan

Ryan Farley,

Sounds great to me. I will register your idea so that our r&d team hopefully would implement it.

Hi Francois,

Thank you for bringing this matter to our attention.

The developer has resolved this issue and published the new version of the application on the Creatio Marketplace.

Please install the latest version via the following link: Advanced list setup for Creatio

Hello...While fixing the previous bug...I believe another one came up.

When accessing a CASE (or any object), if you click on the ACCOUNT of the CASE and come back...for some reason the system doesn't know where it was and keeps displaying the Loading Icon with a brighter screen.

He're a short video to help you understand the problem :



vtq-media.com/Video-Library/BUG-display-when-returning-from-a-detail-page.mp4

Can you fix that ?

SEE CASE below opened to Support@creatio.com 

Case #SR-01273076: VTQ-CANADA - Bug display when returning from a detail page

Oleg Drobina  (Creatio Support)

2/29/2024 at 1:31 PM

Hello Francois,



Thank you for the video and the explanation!



After studying the behavior, we could reproduce it out-of-the-box after installing this Marketplace addon https://marketplace.creatio.com/app/advanced-list-setup-creatio. This addon directly provokes the behavior you've described.

 

Any updates on that issue ?

Hello ,

You can Create Dynamic Folder based on their name . Please see the Attachment.

smit suthar,

Thanks Smith, I know to do this, but I have dozens of Lookups, for this reason I want to do a Dynamic Folder of LOOKUPS using the Starting as Using the Name (with my own prefix) or specifiing the package... But don't know how to get this filter (repeat for lookups)

Thanks again

Hello Julio.Falcon_Nodos,



You can create a dynamic folder and add "starts with" filtering for your prefix.

Anton, I have no access to object Code, I mean the internal code name of the lookup. What you get there is the name, localizable, not unique of the lookup, what I need to access is what you see in the image, below, and select "Code starts with Ndos" or "Package = Nodos.BirthdayGreeting"  to get all lookups created in the package in the folder.

Anton Starikov,

Anton, when I saw Name I refer to the internal code name, not to the localizable Name of the lookup, see my comment above. Thanks

You have to turn on Access rights by records in ProjectFolder object

Permissions on entries in the ProjectFolder object are enabled, but permissions settings are not. I guess I didn’t formulate the question very correctly, the permission settings for dynamic groups (folders) are not displayed

Gevorgyan Tigran,

Hi Gevorgyan,

the same thing happens with Event section

If you re-login to creation everything works finr

Dear Kavian,



Yes, it will be better to create a dynamic folder and use "Add from folder".



Best Regards,

Ivanna Yatsura.

Hi,

Static folders are filled manually and dynamic folders are filled automatically according to the filters set for specific folder. To exclude records from dynamic folder it must be altered in a way that makes it not suitable for such folder. "Exclude from folder" can be used only for static folders.

Angela Reyes,

 Alright thanks :)

Dear Brian,

Basically you can filter the records by tag using 2 ways - special button Tag and filter.

Simply click on Tag and start typing the name of your tag.

Or add filter by object [Knowledge base record tag (by column Object)], add tag=SelectTag.

If you want to find all records having tag that contains certain text in the name you can use Tag.Name. 

Here are 3 ways mentioned above - http://prntscr.com/jsb5n8.

With best regards,

Oliver

Oliver,

THANKS!

I could not find how to set the object to "exists", so I selected Count > 0 and did this:  

Works real nice. 

Hello Brian,

It is possible to set the filter the way you did, though just for your information you can use 'exists' by clicking on 'count' directly.

Lisa

Hi Catherine!

The contacts of portal users can be identified within dynamic folder which will look as following: 

Best regards,

Diana Adams