How to make Case description readonly after save?

RE: How to make Case description readonly after save?

Roland Cadavos — Wed, 17 Feb 2016 04:36:10 GMT

thanks for this Ajay Kumar i guess ill stick with the javascript you gave me.. hmm this would also suffice. thanks for giving all the solution either by php or js. :-)

Regards,

Longki

RE: How to make Case description readonly after save?

Ajay Kumar — Wed, 17 Feb 2016 03:56:32 GMT

Hi Longki,

You have to make few changes in your dependency code to make it work when it is saved.You have given triggerFields as description,so dependency will get triggered,when we filled value for that.

But,If you want to make it readonly once it is saved,you have to remove description field from triggerFields.Then it will work properly.

Here is the modified dependency code.check it out.

<?php
$dependencies['Cases']['description_readonly'] =    array(
    'hooks' => array("edit"),
    'trigger' => 'true', //check if  the field has a value so that it will trigger
    'triggerFields' => array( ),
    'onload' => true,
    //Actions is a list of actions to fire when the trigger is true
    'actions' => array(
        array(
            'name' => 'ReadOnly',
            //The parameters passed in will depend on the action type set in cases.description field
            'params' => array(
                'target' => 'description',
                'value'=> 'not(equal($description,""))',
            ),
        ),
    ),
);

RE: How to make Case description readonly after save?

Roland Cadavos — Wed, 17 Feb 2016 01:52:14 GMT

Found the very correct solution emailed by Ajay Kumar to me :-) as for the latter after you hover out to the field it will be automatically set to readonly even if you havent saved it yet. Here's the fix.

QOUTE from Ajay:

Hi Longki,

Good day too!

1.You can make certain fields readonly by writing dependency.

2.If you want to make it fields to be readonly only specific views, you can try below.

Extend "buildGridsFromPanelsMetadata" this method to custom,and push your fields into this.noEditFields variable,this is how sugar is making fields readonly.

Below is the code snippet,you can copy this code and make changes according to your condition.I tried in recordview.

Note:we no need to call this method on initialize.

_buildGridsFromPanelsMetadata:function(panels){

        var noEditFields = new Array();
        this._super('_buildGridsFromPanelsMetadata',[panels]);
        noEditFields.push('phone_alternate');
        this.noEditFields=noEditFields;
    },

Thanks & Regards

AjayKumar B

HTH,

Longki Dela Cruz

RE: How to make Case description readonly after save?

Roland Cadavos — Tue, 16 Feb 2016 11:00:21 GMT

i solved it using this http://support.sugarcrm.com/Documentation/Sugar_Developer/Sugar_Developer_Guide_7.6/Extension_Framework/Dependencies/

i created a file /custom/Extension/modules/Cases/Ext/Dependencies/description_readonly.php

<?php

$dependencies['Cases']['description_readonly'] = array(

'hooks' => array("edit"),

'trigger' => 'not(equal($description,""))', //check if the field has a value so that it will trigger

'triggerFields' => array('description'),

'onload' => true,

//Actions is a list of actions to fire when the trigger is true

'actions' => array(

array(

'name' => 'ReadOnly',

//The parameters passed in will depend on the action type set in cases.description field

'params' => array(

'target' => 'description',

'value' => 'true',

);

then created a blank file /custom/modules/Cases/Ext/Dependencies/deps.ext.php

so that after Quick Repair and Rebuild the description_readonly.php will be merged there.

after QRR you will find in that file the auto-generated merging of codes..

<?php

// WARNING: The contents of this file are auto-generated.

//Merged from custom/Extension/modules/Cases/Ext/Dependencies/description_readonly.php

$dependencies['Cases']['description_readonly'] = array(

'hooks' => array("edit"),

'trigger' => 'not(equal($description,""))', //check if the field has a value so that it will trigger

'triggerFields' => array('description'),

'onload' => true,

//Actions is a list of actions to fire when the trigger is true

'actions' => array(

array(

'name' => 'ReadOnly',

//The parameters passed in will depend on the action type set in cases.description field

'params' => array(

'target' => 'description',

'value' => 'true',

);

HTH,

Longki

RE: How to make Case description readonly after save?

Roland Cadavos — Tue, 16 Feb 2016 08:22:17 GMT

Hi Sohan Tirpude,

THanks for the reply. In the _render function sir?

Regards,

Longki

RE: How to make Case description readonly after save?

Sohan Tirpude — Tue, 16 Feb 2016 07:48:34 GMT

Hello Longki,

You can js code like this,

 $('#description').prop('readonly', true);

Let me know, if it works or not.

RE: How to make Case description readonly after save?

Roland Cadavos — Tue, 16 Feb 2016 04:52:01 GMT

is there a way using logic hooks after save wherein the fields['description'][readonly]=true;?

or any js to make this possible? readonly in editview?

RE: How to make Case description readonly after save?

Liam Hastings — Mon, 15 Feb 2016 14:16:51 GMT

Roland Cadavos

You can change the arrangement slightly to your personal preference, but when I done this I set Field 1's formula to be show Field 1 when Field 2 is empty. For Field 2 I set the formula to be show Field 2 when Field 2 is not empty. This means that the fields only swap once Field 2 is set.

The principal is the same for both really, however rather than having Field 2 as calculated I created a simple Advanced Workflow to copy the value across upon the record being saved. This worked nicely as it means the fields don't actually swap over until the record is created. I then put a Role in that specifies Field 2 is Read Only for the User I set.

RE: How to make Case description readonly after save?

Roland Cadavos — Mon, 15 Feb 2016 12:42:49 GMT

Can you also post the things you done wherein a set of authorised Users could edit the field and I utilised Advanced Workflow instead of having a calculated field.

RE: How to make Case description readonly after save?

Roland Cadavos — Mon, 15 Feb 2016 12:28:35 GMT

Liam Hastings,

I have cloned the default description(Field1) textfield in studio under Case module, i named it description_c (Field2).

Checked dependent: visible if formula: not(equal($description,"")).

Am i doing the correct solution?

Additional question: What is the formula for Field1? :-)

Thanks,

Longki

RE: How to make Case description readonly after save?

Liam Hastings — Mon, 15 Feb 2016 11:57:34 GMT

Roland Cadavos

That is fine, it just means that if they make a mistake when initially creating the Case that nobody will be able to fix the issue. This is the only reason I want to bring it to your attention as I conveniently done this last week for a customer, where I made it so that only a set of authorised Users could edit the field and I utilised Advanced Workflow instead of having a calculated field.

If that is what you want then one want 2 fields.

Field 1

Allows you to enter the Case text, set to not be shown via dependency when Field 2 is not empty.

Field 2

Shows the value of Field 1, set vie dependency to show when it is not empty.

This is the setup for the fields to swap other. Personally I would have only field 2 as reportable so you don't see it twice in reporting and have each field as a single column (one on top of the other). The reason I would do the single columns on top of each other is that when Field 1 hides and Field 2 shows, you don't notice much of a difference so it is not a big change for the User.

RE: How to make Case description readonly after save?

Roland Cadavos — Mon, 15 Feb 2016 10:57:26 GMT

Liam Hastings

Yes, so that they will be forced to add Note on the Case because the description has been disabled after saving.

Thanks,

Longki

RE: How to make Case description readonly after save?

Liam Hastings — Mon, 15 Feb 2016 10:35:58 GMT

Roland Cadavos,

If you need it to be locked for all Users once it has been entered, that means that nobody will ever be able to change it without importing and updating or mass updating the record. Is this what you want?

RE: How to make Case description readonly after save?

Roland Cadavos — Mon, 15 Feb 2016 10:08:26 GMT

Hi Liam,

How about locked out of all user wherein after saving, it will be on read.only on all views.

Thanks,

Longki

RE: How to make Case description readonly after save?

Liam Hastings — Mon, 15 Feb 2016 10:01:02 GMT

Hi Roland Cadavos,

Ah so you have Advanced Workflows, this opens up a new option where you could use this. It depends on the specifics for how you want this to work, and if you need authorised users to be able overwrite the entered text or if it should be locked out for all Users.

RE: How to make Case description readonly after save?

Roland Cadavos — Mon, 15 Feb 2016 09:42:46 GMT

Hi Liam,

Im using Sugar Enterprise 7.6. Can help me get through this? :-)

Thanks,

Longki

RE: How to make Case description readonly after save?

Liam Hastings — Mon, 15 Feb 2016 09:05:04 GMT

Roland Cadavos,

I presume that you only want it to become read-only once it has been populated with something. There are a few ways that you can do this, with each option depending slightly on the version/edition of Sugar you are using and the exact rules that need to be enforced.

However a base level resolution for this is to create a duplicate description field and make one a calculated field to copy the value of the other. You would then set dependencies so that the initial fields hides when the calculated one is populated with something, and use the same principal on the calculated field. This will make it look as if the field is suddenly becoming read-only, where in fact it is simply swapping the fields over.

If you are looking for something more than this let me know.