I have been testing/playing with portals recently and I am wondering if it's possible to have the same ability to edit an object in the portal interface as the regular interface. I am asking this because in the regular interface I was able to edit all the non read-only fields from a class but not in the portal interface even though I specified <opening_mode>edit</opening_mode> in my brick setup like below:
I made sure the user profile has the full access to the Location class and still there are no editable fields presented in the portal. I would appreciate if someone can provide some insight on this topic!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Out of the box, in the standard portal, there is no scope defined for the Location class.
It is not enough to define a Brick, you should also
* Define a Form, to specify which fields of the Location you want to display and allow to edit
* Define the Scope read and write for the Location Class
Remember that out of the box in a Portal nothing is allowed unless you explicitly allow it.
There are tutorials on how to adapt the Portal, but it's clearly not the easiest part...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a similar question. I created a new brick to display pc infos in portal interface. I want some PC attributes (move2production, purchase_date, end_of_warranty) to be in edit mode. Below is part of my portal datamodel. I created a new profile which has right to edit PC class and added the test user account to this profil. I put oql_edit for PC class as you can see as below. I removed "read_only" flage for the dates. But I have error as attached. Could you advise what is missing ?
<?xmlversion="1.0"encoding="UTF-8"?><itop_designxmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"version="1.6"><module_designs><module_designid="itop-portal"xsi:type="portal"_delta="merge"><bricks><brickid="inventory-for-portal-users"xsi:type="Combodo\iTop\Portal\Brick\ManageBrick"_delta="define"><active>true</active><rank><navigation_menu>60</navigation_menu></rank><width>6</width><title><default>Inventaire</default></title><decoration_class><default>fcfasfa-warehousefc-2x</default></decoration_class><oql><![CDATA[SELECTFunctionalCIWHEREfinalclassIN('Server','PC')]]></oql><fields><fieldid="finalclass"/></fields><display_modes><!--HowthedatacanbedisplayedintheManageBrick--><availables><modeid="list"/><modeid="pie-chart"/><modeid="bar-chart"/></availables><default>list</default></display_modes><grouping><tabs><show_tab_counts>true</show_tab_counts><groups><groupid="Server"><rank>2</rank><title>Serveur</title><condition><![CDATA[SELECTFunctionalCIWHEREfinalclass='Server']]></condition></group><groupid="PC"><rank>1</rank><title>Postesdetravail</title><condition><![CDATA[SELECTFunctionalCIWHEREfinalclass='PC']]></condition></group></groups></tabs></grouping><data_loading>auto</data_loading><export><export_default_fields>true</export_default_fields></export></brick></bricks><forms><formid="pc-view"><class>PC</class><fields/><twig_delta="define"><divclass="row"><divclass="col-sm-6"><fieldset><legend>{{'PC:system'|dict_s}}</legend><divclass="col-sm-6"><divclass="form_field"data-field-id="osfamily_id"data-field-flags="read_only"/><divclass="form_field"data-field-id="osversion_id"data-field-flags="read_only"/></div></fieldset></div><divclass="col-sm-12"><fieldset><legend>{{'Server:moreinfo'|dict_s}}</legend><divclass="col-sm-6"><divclass="form_field"data-field-id="move2production"/><divclass="form_field"data-field-id="purchase_date"/></div><divclass="col-sm-6"><divclass="form_field"data-field-id="end_of_warranty"/><divclass="form_field"data-field-id="description"data-field-flags="read_only"/></div></fieldset></div></div></twig><modes><modeid="edit"/><modeid="view"/></modes></form></forms><classes><classid="PC"_delta="merge"><scopes><scopeid="all"><oql_view><![CDATA[SELECTPC]]></oql_view><oql_edit><![CDATA[SELECTPC]]></oql_edit><allowed_profiles><allowed_profilid="Portal User Inventory"></allowed_profil></allowed_profiles></scope></scopes></class><classid="FunctionalCI"_delta="define"><scopes><scopeid="all"><oql_view><![CDATA[SELECTFunctionalCIJOINOrganizationONFunctionalCI.org_id=Organization.idWHEREOrganization.id=:current_contact->org_id]]></oql_view></scope></scopes></class></classes></module_design></module_designs></itop_design>
You might have to add a oql_edit scope on FunctionalCI with SELECT FunctionalCI WHERE finalclass='PC'
Have you checked the grant matrix of your User, to see if they can read and modify those FunctionalCI and PC objects?
The scopes are just a restriction of a rights which must exists on the Profile(s)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I have been testing/playing with portals recently and I am wondering if it's possible to have the same ability to edit an object in the portal interface as the regular interface. I am asking this because in the regular interface I was able to edit all the non read-only fields from a class but not in the portal interface even though I specified
<opening_mode>edit</opening_mode>in my brick setup like below:I made sure the user profile has the full access to the Location class and still there are no editable fields presented in the portal. I would appreciate if someone can provide some insight on this topic!
Out of the box, in the standard portal, there is no scope defined for the Location class.
It is not enough to define a Brick, you should also
* Define a Form, to specify which fields of the Location you want to display and allow to edit
* Define the Scope read and write for the Location Class
Remember that out of the box in a Portal nothing is allowed unless you explicitly allow it.
There are tutorials on how to adapt the Portal, but it's clearly not the easiest part...
Hi Vincent,
I have a similar question. I created a new brick to display pc infos in portal interface. I want some PC attributes (move2production, purchase_date, end_of_warranty) to be in edit mode. Below is part of my portal datamodel. I created a new profile which has right to edit PC class and added the test user account to this profil. I put oql_edit for PC class as you can see as below. I removed "read_only" flage for the dates. But I have error as attached. Could you advise what is missing ?
Last edit: ines 2025-10-20
You might have to add a oql_edit scope on FunctionalCI with
SELECT FunctionalCI WHERE finalclass='PC'Have you checked the grant matrix of your User, to see if they can read and modify those FunctionalCI and PC objects?
The scopes are just a restriction of a rights which must exists on the Profile(s)