Symptoms

In some cases, not all activities, in which the current or selected user is the owner, are displayed in the [Activities] section. Similar situation can be observed on the [Dashboards]  tab of the section.

Cause

The situation occurs, when the owner does not get into the list of participants automatically after the activity is created (manually or according to the process). In the [Activities] section, filtering is performed by this detail: only records whose [Participants] detail contains a user specified as the section "Owner" in the filter are displayed.

Solution

Correct the custom process or the activity creation logic so that the owner is added to the [Participants] detail once created. After this, add the corresponding missing participants by a script. An example of a script:

INSERT INTO [ActivityParticipant]
([Id], [ActivityId], [ParticipantId], [RoleId])
SELECT NewId(), a.[Id], a.[OwnerId], '53fc4a92-b0ea-e111-96c4-00165d094c12'
FROM [Activity] a
WHERE NOT EXISTS (
SELECT ap.[Id] FROM [ActivityParticipant] ap
WHERE ap.[ActivityId] = a.[Id]
AND ap.[ParticipantId] = a.[OwnerId]
)

Symptoms 

Type: Terrasoft.SyncException%0D%0AСообщение: В процессе синхронизации произошла ошибка%0D%0A%0D%0AТип: Terrasoft.ServerException%0D%0AMessage: Request for server returned an erro%0D%0AAdditional information: %0D%0A%09{"request":{"id":6,"headers":{"X-Terrasoft-Mobile":"true","Accept":"application/json","Content-Type":"application/json","Authorization":"Cookie","X-Requested-With":"XMLHttpRequest"},"options":{"url":"http://xxx.xxx.xxx.xxx/0/Services/ProfileService.asmx/Logout","method":"POST","jsonData":{"customData":"","doLogout":"true"},"headers":{"X-Terrasoft-Mobile":"true","Accept":"application/json","Content-Type":"application/json","Authorization":"Cookie"},"disableCaching":false,"scope":{"initialConfig":{"url":"http://xxx.xxx.xxx.xxx/0/Services/ProfileService.asmx/Logout","method":"POST","jsonData":{"customData":"","doLogout":"true"},"headers":{"X-Terrasoft-Mobile":"true","Accept":"application/json","Content-Type":"application/json","Authorization":"Cookie"},"disableCaching":false},"performanceCounter":{"startDate":"2015-06-08T12:11:51.319Z"}}},"async":true},"requestId":6,"status":500,"statusText":"Internal Server Error","responseText":"System.InvalidOperationException: Request format is invalid: application/json.\r\n   at System.Web.Services.Protocols.HttpServerProtocol.ReadParameters()\r\n   at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()\r\n","responseXML":null,"responseBytes":null}%0D%0A%0D%0A

Cause

A problem in IIS settings.

Solution

Go to the IIS settings - Handler Mappings module

Find the rules for files with * .asmx extension with the following names:

"WebServiceHandlerFactory-Integrated"

"WebServiceHandlerFactory-ISAPI-2.0_32bit"

"WebServiceHandlerFactory-ISAPI-2.0_64bit"

and delete all of them.

Question

How can I add/change color in the "Color customization" section?

Answer

You can add/change the existing color in the "Color customization" section via the source at all-combined.js (…\Terrasoft.WebApp\Resources\ui\combined\all-combined.js). Use the "colors" property in "ColorMenuItem".

Please note that in this case you can only use the color code, since the application specifies that only "background-color" can be used for this property. You will not be able to insert links to images.

Question

How to remove the action in the mobile application and how you can sort the actions?

Answer

Approximate algorithm.



1. You need to create your own module (for example,"TestOrderRemoveMobileAccountModuleConfig")

2. To delete an action, use the following method - Terrasoft.sdk.Actions.remove: function (model, actionName)

For example:

Terrasoft.sdk.Actions.remove("Account", "addAccountAnniversary");

3. Use the following code to sort:

Terrasoft.sdk.Actions.setOrder("model ", {
    "actionName1": 0,
    "actionName2": 1,
    …,
    "actionName5": 4
});

For example:

Terrasoft.sdk.Actions.setOrder("Account", {
    "Phone": 0,
    "Email": 1,
    "Meeting": 2,
    "Terrasoft.ActionCopy": 3,
    "Terrasoft.ActionDelete": 4
});
 

4. Then connect it in the user manifest of the mobile application (available on our SDK) in the “Models” section for the “Account” object (if they are accounts) in the “PagesExtensions” section. For example:

"Models": {
    "Account": {
        "RequiredModels": [],
        "ModelExtensions": [],
        "PagesExtensions": [
            "TestOrderRemoveMobileAccountModuleConfig"
        ]
    },
 

Where TestOrderRemoveMobileAccountModuleConfig is an arbitrary schema name.

 

You can see the implementation of the add address logic in the MobileAccountModuleConfig schema (the action is called addAccountAddress).

Question

The styles for twitter and facebook icons are not applied on the [Communication options] detail after I upgrade to a new version

Answer

A CommonCSSV2 replacing client module ccontaining custom styles has been found in the configuration. The point is that the base styles have slightly changed and have been added in version 7.6.0, but replacing in the custom package does not let apply these changes.

To eliminate the problem, transfer the styles from the CommonCSSV2 base module to the replacing module and add the custom styles in the end. You can also delete the text from the "Source code" module tab - the styles contained thereon will not be applied.

Error message

Terrasoft.Common.ReflectionUtilities FindTypeByShortName - Could not load file or assembly 'SharpSvn.dll' or one of its dependencies. The specified module could not be found.

System.IO.FileNotFoundException: Could not load file or assembly 'SharpSvn.dll' or one of its dependencies. The specified module could not be found.

File name: 'SharpSvn.dll'

at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)

at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)

at System.Reflection.Assembly.LoadFrom(String assemblyFile)

at Terrasoft.Web.Common.AssemblyResolver.FindAssemblyByProcessRunMode(String requestingAssemblyName, String searchSubDirectory)

at System.AppDomain.OnAssemblyResolveEvent(RuntimeAssembly assembly, String assemblyFullName)

Solution

Install Microsoft Visual C++ 2010 Redistributable

Case description:

We want to show different printables for different opportunity stages.

Algorithm of realization:

1.  Create replacing client modules for OpportunityPageV2 and OpportunitySectionV2.
2. Add message that will refresh print button when we work in CombinedMode and add event handler which run when opportunity stage was changed.

   1. OpportunityPageV2

      define("OpportunityPageV2", ["SysModuleReport"], function (SysModuleReport) {
          return {
              entitySchemaName: "Opportunity",
              details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
              attributes: {
                  "Stage": {
                      "onChange": "onStageChanged"
                  }
              },
              messages: {
                  "PrintButtonFilterMessage": {
                      mode: Terrasoft.MessageMode.PTP,
                      direction: Terrasoft.MessageDirectionType.PUBLISH
                  }
              },
              methods: {
                  printButtonFilterPublishMessage: function () {
                      return this.sandbox.publish("PrintButtonFilterMessage", this.get("Stage").value, ["key"]);
                  },
                  onStageChanged: function () {
                      this.printButtonFilterPublishMessage();
                  }
              },
              diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/,
              rules: {},
              businessRules: /**SCHEMA_BUSINESS_RULES*/{}/**SCHEMA_BUSINESS_RULES*/
          };
      });
      

       

   2. OpportunitySectionV2

      define("OpportunitySectionV2", [], function () {
          return {
              messages: {
                  "PrintButtonFilterMessage": {
                      mode: Terrasoft.MessageMode.PTP,
                      direction: Terrasoft.MessageDirectionType.SUBSCRIBE
                  }
              },
              methods: {
                  init: function () {
                      this.callParent(arguments);
                      this.sandbox.subscribe("PrintButtonFilterMessage", this.onPrintButtonFilterMessage, this, ["key"]);
                  },
                  onPrintButtonFilterMessage: function (args) {
                      this.set("StageId", args);
                  }
              },
              diff: []
          };
      });
      

       

3. Override preparePrintFormsMenuCollection method in both pages and add calling of initCardPrintForms() and initSectionPrintForms() on stage changing and PrintButtonFilterMessage handling.

   1. OpportunityPageV2 

      define("OpportunityPageV2", ["SysModuleReport"], function (SysModuleReport) {
          return {
              entitySchemaName: "Opportunity",
              details: /**SCHEMA_DETAILS*/{}/**SCHEMA_DETAILS*/,
              attributes: {
                  "Stage": {
                      "onChange": "onStageChanged"
                  }
              },
              messages: {
                  "PrintButtonFilterMessage": {
                      mode: Terrasoft.MessageMode.PTP,
                      direction: Terrasoft.MessageDirectionType.PUBLISH
                  }
              },
              methods: {
                  preparePrintFormsMenuCollection: function (printForms) {
                      var stage = this.get("Stage");
                      printForms.eachKey(function (key, item) {
                          if (!item.get("Caption")) {
                              item.set("Caption", item.get("NonLocalizedCaption"));
                          }
                          item.set("Tag", key);
                          if (item.get("TypeColumnValue")) {
                              item.set("Visible", { bindTo: "getPrintMenuItemVisible" });
                          }
                          //Here is your logic for filtering of printables
                          /*************************************************************************/
                          if (stage !== undefined) {
                              if (stage.value === "423774cb-5ae6-df11-971b-001d60e938c6") {
                                  if (key === "0d8c28ce-9794-42be-8427-3d5d60e60c1f") {
                                      item.set("Visible", false);
                                  }
                                  else {
                                      item.set("Visible", true);
                                  }
                              } else if (stage.value === "fb563df2-5ae6-df11-971b-001d60e938c6") {
                                  if (key === "c80094c5-2513-4857-b5da-4b355aed8c10") {
                                      item.set("Visible", false);
                                  }
                                  else {
                                      item.set("Visible", true);
                                  }
                              } else {
                                  item.set("Visible", true);
                              }
                          }
                          /*************************************************************************/
                      }, this);
                  },
                  printButtonFilterPublishMessage: function () {
                      return this.sandbox.publish("PrintButtonFilterMessage", this.get("Stage").value, ["key"]);
                  },
                  onStageChanged: function () {
                      this.initCardPrintForms();
                      this.printButtonFilterPublishMessage();
                  }
              },
              diff: /**SCHEMA_DIFF*/[]/**SCHEMA_DIFF*/,
              rules: {},
              businessRules: /**SCHEMA_BUSINESS_RULES*/{}/**SCHEMA_BUSINESS_RULES*/
          };
      });
      

       

   2. OpportunitySectionV2

      define("OpportunitySectionV2", [], function() {
          return {
              messages: {
                  "PrintButtonFilterMessage": {
                      mode: Terrasoft.MessageMode.PTP,
                      direction: Terrasoft.MessageDirectionType.SUBSCRIBE
                  }
              },
              methods: {
                  preparePrintFormsMenuCollection: function(printForms) {
                      printForms.eachKey(function(key, item) {
                          if (!item.get("Caption")) {
                              item.set("Caption", item.get("NonLocalizedCaption"));
                          }
                          item.set("Tag", key);
                          if (item.get("TypeColumnValue")) {
                              item.set("Visible", {bindTo: "getPrintMenuItemVisible"});
                          }
                          //Here is your logic for filtering of printables
                          /*************************************************************************/
                          if (this.get("StageId") !== undefined) {
                              if (this.get("StageId") === "423774cb-5ae6-df11-971b-001d60e938c6") {
                                  if (key === "0d8c28ce-9794-42be-8427-3d5d60e60c1f") {
                                      item.set("Visible", false);
                                  }
                                  else {
                                      item.set("Visible", true);
                                  }
                              } else if (this.get("StageId") === "fb563df2-5ae6-df11-971b-001d60e938c6") {
                                  if (key === "c80094c5-2513-4857-b5da-4b355aed8c10") {
                                      item.set("Visible", false);
                                  }
                                  else {
                                      item.set("Visible", true);
                                  }
                              } else {
                                  item.set("Visible", true);
                              }
                          }
                          /*************************************************************************/
                      }, this);
                  },
                  init: function() {
                      this.callParent(arguments);
                      this.sandbox.subscribe("PrintButtonFilterMessage", this.onPrintButtonFilterMessage, this, ["key"]);
                  },
                  onPrintButtonFilterMessage: function(args) {
                      this.set("StageId", args);
                      this.initSectionPrintForms();
                      this.initCardPrintForms();
                  }
              },
              diff: []
          };
      });
      

      !!!IMPORTANT!!! - in preparePrintFormsMenuCollection() you can change code only between comments

      Identificators of printables you can get from SysModuleReport table in you DB

Question

The customer experiences problems with searching Contact duplicates. Bpm'online finds duplicates, the duplicate page is opened, but when the [Save] button is clicked, nothing happens.

Answer

The problem is that the customer replaced the "Contact" object and set its "Email" field as "required". If you deselect this setting option, the duplicates will be merged without errors. If a user needs to make the "Email" field population required without impacting the base functionality, this must be done via business rules:

https://academy.bpmonline.com/documents/technic-sdk/7-13/business-rules…

Symptoms

"The error code is 0x803F7000" error when installing bpm'online mobile 7 for Windows 10.

Cause

The error is related to the local settings of Windows 10. Possible reasons for the error:

• Windows Store Cache.
• Wrong date and time.
• Windows is not activated.
• Microsoft server is overloaded.

Solution

Links that describe the cause and solution of this problem:

-    http://answers.microsoft.com/en-us/windows/forum/windows_10-win_upgrade/error-code-0x803f7000-in-windows-store-10/18f61f6f-009a-435f-8d33-6956e301a849?auth=1

-    http://www.fixerrs.com/2015/09/fix-error-0x803f7000-windows-10-store.html

-    http://errortools.com/windows/how-to-fix-windows-10-error-code-0x803f7000/

-    http://microsoftfixnow.com/error-code-0x803f7000-windows-10-while-accessing-windows-store/

Question

How can I add a label to a section page? We can add columns when configuring section page settings. What about adding a string with a fixed label in it and not a column, can we add it? 

Answer

In the configurator, in your section page schema, add a localized string and the following code in the diff property:

{
    "operation": "insert",
    "name": "UsrTestLabel",
    "values": {
        "layout": {
            "column": 12,
            "row": 0,
            "colSpan": 12,
            "rowSpan": 1
        },
        "itemType": Terrasoft.ViewItemType.LABEL,
        "caption": {
            "bindTo": "Resources.Strings.UsrTestLabelString"
        }
    },
    "parentName": "Header",
    "propertyName": "items"
},

The "layout" block describes the element location and size.