Changes made in Code On Time

In order to preserve the promise of transparency and open communication, the change log records changes to topics made by both customers and employees. Anyone can dispute a change by clicking the "Dispute" link and entering additional details.


  • August 14, 2018 09:06
    Zhan Hui, the poster:
    Reason: removed by the poster
  • August 09, 2018 17:19
    Dennis Bykkov
    Changed reply in topic of REST issues by Dennis Bykkov to Paul,<br /><br />The behavior works like the following:<br /><br /><ol><li>If no Accept header is provided and no "_dataType" query string argument is provided, it attempts to return XML.</li><li>If the Accept header is set to "application/javascript", "text/javascript", "application/javascript", "application/ecmascript", or "application/x-ecmascript",&nbsp;it returns a jsonp supported JS expression (a bit of javascript wrapping the JSON)</li><li>If "_dataType" query string argument is set to "json", we assume you are trying to make a jsonp request and set the accept type to "application/javascript".</li><li>If you pass the header Accept with the value: "application/json", we will return properly encoded JSON.</li></ol>Your solution here is to add the header&nbsp;<br /><br /><pre>Accept: application/json</pre>We are evaluating improvements and a potential overhaul to the REST API feature for future releases..
  • August 04, 2018 01:49
    Ossama, the poster:
    Reason: removed by the poster
  • August 03, 2018 17:22
    Brandy Riggs, the poster:
    Reason: removed by the poster
  • August 03, 2018 17:17
    Brandy Riggs, the poster:
    Reason: removed by the poster
  • August 02, 2018 21:42
    Dennis Bykkov
    Changed reply in topic of Need to Remove the Splash Screen Permanently by Dennis Bykkov to Brandy,<br /><br />You can disable the splash screen by using the property "splash.enabled". The splash object should be at the top of the touch-settings (not under ui property).<br /><br /><pre>{ "splash": { "enabled": false }}</pre>Paul,<br /><br />Much like most fashion, it seems to go in circles. Currently, splash screens are required for iOS apps (<a href="https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/launch-screen/" rel="nofollow" target="_blank" title="Link https//developerapplecom/design/human-interface-guidelines/ios/icons-and-images/launch-screen/">https://developer.apple.com/design/human-interface-guidelines/ios/icons-and-images/launch-screen/</a>) and recommended for Android (<a href="https://material.io/design/communication/launch-screen.html#usage" rel="nofollow" target="_blank">https://material.io/design/communication/launch-screen.html#usage</a>). They are also in use for Windows apps. We have opted to add them in by default and added a switch to control the behavior..
  • July 23, 2018 16:37
    Dennis Bykkov
    Changed reply in topic of Advice on cleaning Controllers.log.xml file by Dennis Bykkov to John,<br /><br />You should be able to right-click the command and press "Reset to Baseline" in the Project Designer..
  • July 20, 2018 02:24
    boonchoo chatsrinopkun
    Changed description of requirement likes filter to display only some nw territories ... i tried context fields on an m2m but it displayed without the padsing values by boonchoo chatsrinopkun to requirement likes filter to display only some nw territories ... i tried context fields on an m2m but it displayed without using the passing values. all values are displayed.
  • July 20, 2018 02:18
    boonchoo chatsrinopkun
    Changed reply in topic of Vote to save COT Excel Tools by boonchoo chatsrinopkun to i recently work on node virtualization to dynamically manage behaviours of all views, fields and actions of all controllers ... it is a great investment. \ managing data can be done using before/afterSqlAction i don't think i need excel anymore since it requires manual updates via ide .., it is great to batch update code settings but keeping these settings in db and dynamically adjust accordingly fits better to my needs.
  • July 18, 2018 11:33
    Steven Wright, the poster:
    Reason: removed by the poster
  • July 18, 2018 03:00
    Brad Gall, the poster:
    Reason: removed by the poster
  • July 13, 2018 00:39
    boonchoo chatsrinopkun, the poster:
    Reason: User-initiated delete from community
  • July 04, 2018 20:49
    Customer Service
    Reason: Inappropriate solicitation
    Dispute this change
  • July 03, 2018 07:11
    Atomic Simply, the poster:
    Reason: removed by the poster
  • July 01, 2018 08:55
    Bernard
    Changed reply in topic of Purpose of Controller.Log.xml file? by Bernard to Hi Tom, <br /><br />I only noticed this functionality from experience and not according to the norm- I take it one step further using field order too and always revert back to the model for any changes I can do. I’m not saying you’ve done this incorrectly at all. (Maybe you’ve done it best for team work)<br />However I don’t believe even COT realises the potential that this area(model) can be used as the primary development/design area containing the field order and field settings, page names to be applied to all forms in the app (until one needs to change something specifically in a form then that little change becomes the override for that field only). <br /><br />I’m sure there’s a way of synchronising the model to either your grid field list or to the edit form without losing too much changes, then all forms follow suit in future changes in the model. I think it might be a matter of synchronising field settings in two files per controller but I haven’t investigated yet what the links are. I have many old projects that are “designer” developed I’d also like to relink. <br />(NB the function to restore/revert to baseline is not what would be best because you will lose your designer changes!). <br /><br />What would be amazing in COT is to have more design settings in the model area so we also only make changes once (also so that there’s one place to go to FIRST when starting a project for everyone. )<br />For example I would love to have a function to assign formula fields once or twice only for the lookup for all forms in the model tool where lookup occurs instead of going to designer afterwards and applying it - Also to assign “$autocompleteanywhere” once per controller until removed manually for specific fields. Just examples. <br /><br />I would suggest trying out the next new project reverting to model first only arranging field order there and then hiding unwanted form fields in designer (not deleting or moving them). Any new reordering still done in modeller will apply in all forms. Any renaming also do in model area and NB need to rename internally as COT goes out of sync. Watch out for aliasing the right fields in the model. <br /><br />Good luck..
  • July 01, 2018 08:53
    Bernard
    Changed reply in topic of Purpose of Controller.Log.xml file? by Bernard to Hi Tom, <br /><br /> I only noticed this functionality from experience and not according to the norm- I take it one step further using field order too and always revert back to the model for any changes I can do. I’m not saying you’ve done this incorrectly at all. (Maybe you’ve done it best for team work)<br /> However I don’t believe even COT realises the potential that this area(model) can be used as the primary development/design area containing the field order and field settings, page names to be applied to all forms in the app (until one needs to change something specifically in a form then that little change becomes the override for that field only). <br /><br /> I’m sure there’s a way of synchronising the model to either your grid field list or to the edit form without losing too much changes, then all forms follow suit in future changes in the model. I think it might be a matter of synchronising field settings in two files per controller but I haven’t investigated yet what the links are as I have many old projects that are “designer” developed <br /> (NB the function to restore/revert to baseline is not what would be best because you will lose your designer changes!). <br /><br /> What would be amazing in COT is to have more design settings in the model area so we also only make changes once (also so that there’s one place to go to FIRST when starting a project for everyone. )<br /> For example I would love to have a function to assign formula fields once or twice only for the lookup for all forms in the model tool where lookup occurs instead of going to designer afterwards and applying it - Also to assign “$autocompleteanywhere” once per controller until removed manually for specific fields. Just examples. <br /><br /> I would suggest trying out the next new project reverting to model first only arranging field order there and then hiding unwanted form fields in designer (not deleting or moving them). Any new reordering still done in modeller will apply in all forms. Any renaming also do in model area and NB need to rename internally as COT goes out of sync. Watch out for aliasing the right fields in the model. <br /><br /> Good luck..
  • June 28, 2018 18:24
    Dennis Bykkov
    Reason: Harassment
    Dispute this change
  • June 28, 2018 18:24
    Dennis Bykkov
    Reason: Harassment
    Dispute this change
  • June 28, 2018 18:24
    Dennis Bykkov
    Reason: Harassment
    Dispute this change
  • June 28, 2018 18:24
    Dennis Bykkov
    Reason: Harassment
    Dispute this change
next » « previous