|
Q1
|
Why am I getting an error when trying to access the EJB component?
|
|
A1
|
If you have JDK version 1.5 installed on your computer, the EJB component will not work. Try installing JDK version 1.4.
Note: A project cannot work with both the EJB component and the Web Service component, since the Web Service component needs to work with JDK version 1.5.
|
|
|
|
|
Q2
|
Why do I receive a ‘Source directory does not exist’ error when using the Directory Scanner component (as a step or as a trigger) to move a file that is located on another server (remote access)?
|
|
A2
|
When Magic xpi is installed as a service, and you want to work remotely (with Directory Scanner or any other component), you should verify that:
-
The remote directory permissions are set correctly.
-
This directory is accessible remotely from the Magic xpi machine.
If both of these requirements have been verified, you should then check the Magic xpi service configuration. The Magic xpi service should be configured with an Account and not a local Log On. (Note that, by definition, a service that is configured with a local Log On is limited to local activities only.)
You need to create a new designated user, grant that user the required rights, and use this user in the service configuration. Log on with this user to the system to start the service. Make sure you do not log out from the system when you are logged as this user.
|
|
|
|
|
Q3
|
The File Management component's Command Line method does not work, and the "Error 207: Failed to execute command line" error message is generated. Why does this happen?
|
|
A3
|
The File Management component's Command Line method does not work when the path to the executable file includes spaces. For example, a space in a directory name: 'c:\Magic xpi files'. The executable file cannot be started, and the following error message occurs:
Error 207: Failed to execute command line
To prevent this from happening, you should use double quotes in the Execute File Name parameter. For example, "c:\Magic xpi files".
|
|
|
|
|
Q4
|
How do I overcome the "Error 24: Error Code [###] does not exist for the selected component [##]" error?
|
|
A4
|
To overcome this error, follow these steps:
-
In the Magic xpi Studio:
-
Go to Project menu, and select Errors.
-
Click the Components button and make sure that your component is selected.
-
Select your component from the drop-down list.
-
If you see the relevant errors, the problem is solved.
-
If step 1 does not solve the problem:
-
Create a new project.
-
Save the project.
-
Export and import the flows from your project.
|
|
|
|
|
Q5
|
When using the Dynamics CRM connector to add an attachment to an email, I cannot open the attachment through the Magic xpi Studio and I get the "Error 1250: Dynamics CRM call error: com.magicsoftware.ibolt.dynamicscrm.IBDynamicsCRMException: createOperation (AxisFault): Server was unable to process request." Error. How can I prevent this happening?
|
|
A5
|
To successfully open such an attachment, you first need to convert the body of the email from BLOB to Base64 with the BlobToBase64 function. For example, BlobToBase64 (File2Blb ('D:\1.txt')).
|
|
|
|
|
Q6
|
Why can't I find one of the newly-released components in my project?
|
|
A6
|
-
If you migrate your project from an earlier version that did not contain a specific component, the component will not be available in your migrated project even after the migration process. You will need to add the component manually.
In the Component Repository, click the Add button. This opens the Add Components to the Project dialog box. This dialog box contains a list of all user components that are under the \UserComponents directory and the components from the ifclib folder (the components that are not part of the current project).
The folder name must be identical to the component name. Here, you can select the required component.
-
In addition, a number of components were released after the official release of Magic xpi 4.1, such as the Dynamics AX connector and the Google Drive connector. Each of these components has a separate installation, which are available in the Downloads area. If you do not have access to the Downloads area, contact the Tech Support department.
|
|
|
|
|
Q7
|
Why am I getting the "Cannot find component <Installation>\ifclib" error?
|
|
A7
|
This error appears when you use a user-defined component and the flow is imported into a different machine or installation. In this scenario, you need to add the component manually.
To add the component manually, click the Add button in the Component Repository. This opens the Add Components to the Project dialog box. This dialog box contains a list of all user components that are under the \UserComponents directory and the components from the ifclib folder (the components that are not part of the current project).
The folder name must be identical to the component name. Here, you can select the required component.
|
|
|
|
|
Q8
|
Why are the characters corrupted in the body of an email?
|
|
A8
|
When sending an email from Magic xpi using the Email component, characters in the email's body might not be displayed properly due to incorrect encoding. The same message in the Monitor is displayed correctly.
To properly display these characters in the email's body, you need to define an email character set. To do this, you should manually add the following line to the Magic.ini file's [MAGIC_ENV] section:
MailCharset = [proper encoding]
For example, the correct encoding for Hebrew in Windows is 1255.
Note: If you do not define a character set, the system's charset will be used by default.
|
|
|
|
|
Q9
|
Why can't I validate my Google resource?
|
|
A9
|
When you click the Google Resource Setting window's Validate button, and the StoredCredential file does not exist under the <Magic xpi installation>\projects\DAX\resource\Google\<resource name>\credentialsdatastore folder, a new StoredCredential file is created. However, this newly created StoredCredential file is not valid as it does not contain the client_secrets token. This causes the validation process to fail. In this situation, you need to perform the OAuth 2.0 authorization flow again, from the beginning, to create a valid StoredCredential file.
A valid StoredCredential file is a file that was retrieved from the Google server after performing the OAuth 2.0 authorization flow. After the completion of the validation process, the StoredCredential file is recognized as a valid one. This is why the file's Date modified field is changed when you click OK upon receipt of the validation success message.
|
