Nova postagem

Pesquisar

Discussão
· Abr. 28

Let's talk about the new UI for Interoperability and Data Transformations editor

It's been a while since the new UI for Productions and DTL was published as a preview and I would like to know your opinions about it.

WARNING: This is a personal opinion, totally personal and not related with InterSystems Corporation.

I'm going to start with the Interoperabilty screen:

Production screen:

The style is sober and without frills, following the line of cloud services design, I like it.

But, always a but...or maybe two:

In my opinion there is too much information, the left menu is superfluous, it's true that you can collapse it, but I don't want to do it each time that I use the screen. I don't need to see all the time all the productions in my NAMESPACE, the Production Items, Rule Sets and Data Transformations. I feel that the designers have suffered a case of "horror vacui"

About these menus, looks like the options are too close:

And displaying Rule and Data Transformations editors in the same screen for small screens like a laptop it's a scrolling nightmare:

 A pop-up window with the editors would be more "clean" for the common user. A positive point is that we can select how we want to open the editors.:

But maybe we have too much options.

DTL Editor:

Well, I like it, the design is simple and clear, maybe, as in the Production screen, the lines are too close together and we have lost the drag and drop to link fields.

Conclusion:

The design has been modernized and looks nice, but in my opinion as a former web developer "less is more". I would like to work with simpler screens   with a well defined behaviour, I don't need to access from the same screen to all the interoperability functionalities.

My two cents, we need to balance functionalities and a friendly and modern user interface, the new design seems to go in that direction. Thank you to all the team involved in the development!

5 novos comentários
Discussão (5)4
Entre ou crie uma conta para continuar
Resumo
· Abr. 28
Pergunta
· Abr. 27

I want to use ollama and IRIS for my AI use case - How do I connect to ollama?

I combined @Rodolfo Pscheidt https://github.com/RodolfoPscheidtJr/ollama-ai-iris with some files from @Guillaume Rongier https://openexchange.intersystems.com/package/iris-rag-demo.

My own project is https://github.com/oliverwilms/ollama-ai-iris

I can run load_data.py and it connects to IRIS (same container).

When I try to run query_data.py https://github.com/oliverwilms/ollama-ai-iris/blob/main/query_data.py , it cannot connect to ollama:

ConnectionError: Failed to connect to Ollama. Please check that Ollama is downloaded, running and accessible.

I wonder if I need to add in query_data.py, how it can "find" ollama which is  in docker-compose.yml?

https://github.com/oliverwilms/ollama-ai-iris/blob/main/docker-compose.yml

3 novos comentários
Discussão (3)2
Entre ou crie uma conta para continuar
Pergunta
· Abr. 26

Como transferir um arquivo que se encontra em um computador remoto para o servidor onde está instalado o IRIS, através de CSP?

Oi Pessoal,

Por favor,

Gostaria de um exemplo de código csp para tranferir um arquivo xml, txt, csp para o servidor onde se encontra instalado o IRIS.

Obrigado,

Edilson

1 novo comentário
Discussão (1)1
Entre ou crie uma conta para continuar
Pergunta
· Abr. 26

Which DB Resource to provide to a web application related role for a deployed app?

Hi developers!

While developing web apps the security practice I consider safe and convenient is to create a special Role (e.g. equal application name) which contains security resources which application will need (SQL tables, priviledges, database access, etc) and assign it to the Web Application.
So the user gets this role once it loggs in to the application (via password, no password or delegated).

Convenient, right?

So, the question is, when I deploy the app as an IPM module what should I put as a database access?

For example I develop the app in the USER namespace so I list the access to %DB_USER in Role's resources and the export(D ##class(Security.Roles).Export("/home/irisowner/dev/roles.xml",,"lovable",,1) looks like:

<?xml version="1.0" encoding="UTF-8"?>

<RolesExport>

<Roles>

<Name>lovable</Name>

<Version>4</Version>

</Roles>

<Roles>

<GrantedRoles>

<GrantedRolesItem>%DB_USER</GrantedRolesItem>

</GrantedRoles>

<Name>lovable</Name>

<Version>4</Version>

</Roles>

<SQLPrivileges>

<Namespace>USER</Namespace>

<SQLObject>1,dc_Sample.Person</SQLObject>

<Privilege>s</Privilege>

<Grantee>lovable</Grantee>

<Grantor>SuperUser</Grantor>

<Grantable>0</Grantable>

</SQLPrivileges>

<SQLRoleGrantOption>

<UserOrRole>lovable</UserOrRole>

<RoleGranted>%DB_USER</RoleGranted>

<Grantable>0</Grantable>

</SQLRoleGrantOption>

</RolesExport>

But the app could be installed in any database, right? Which resource should I provide? Maybe %DB_DEFAULT (What does it mean BTW)? Any ideas?

4 novos comentários
Discussão (4)3
Entre ou crie uma conta para continuar