Vault Application

You have asked this question in multiple places.  Please do not do that as it duplicates effort.  Your question has been answered in the Developer group: (+) VAF Application - Developer Forum - Developers - M-Files Community by Laurent Gabiot who pointed you at the documentation here: https://developer.m-files.com/Frameworks/Vault-Application-Framework/Distributing-Child-Applications/.

Apology for multiple posts for the question, however, I have tried and it is not working the way it is advised.
1. I have used the server app guid in client.
2. compiled the client app and created .mfappx.
3. using this .mfappx in server application with below code

 

public override void Initialize(MFilesAPI.Vault vaultSrc)
{
try
{
SysUtils.ReportToEventLog($"The application path is {Directory.GetCurrentDirectory()}", System.Diagnostics.EventLogEntryType.Information);
string appPath = "app.mfappx";

if (File.Exists(appPath))
{
vaultSrc.CustomApplicationManagementOperations.InstallCustomApplication(appPath);
}
else
{
SysUtils.ReportErrorToEventLog("File: " + appPath + " does not exist");
}
}
catch (Exception ex)
{
if (!MFUtils.IsMFilesAlreadyExistsError(ex))
SysUtils.ReportErrorToEventLog(ex.Message);
}

base.Initialize(vaultSrc);
}

it says in event logs
The system cannot find the file specified. (app.mfappx)
please note that app.mfappx is also installed as an application

The client app GUID must be different from your server app GUID.

Your client app's appdef.xml needs a <master-application-guid> tag which references the server app's GUID as content, like so: <master-application-guid>eb1ec555-b326-46df-899b-8ece191a08bd</master-application-guid>

See https://developer.m-files.com/Frameworks/User-Interface-Extensibility-Framework/Application-Definition/ 

Thank you Dr. Martin Lisowski I see the master-application-guid was the right def.xml which shows them child under the parent. So I hope now child application will be able to communicate and access values from within the parent-app. The idea behind this is that we want a value, specifically, the class value to be set in configuration of Vault and make this class readable from client application. 

Needful in these lines will be helpful.

Thanks you once again

Simply bundling the applications will not do this.  You need to create a vault extension method in the VAF application which returns the data you need, then call that from the UI application.

Thank you Craig Hawker , 

I agree with you and i have created a comprehensive Vault application that interacts with the external Web Service, in fact for a signing solution. It works fine. Now there was a requirement to exchange the information between Vault Server(e.g. taking class name set in the configuration) and accessing it in UI application. 
I was expecting a guide that could help me grab the class name from Server Configured and accessed in UI. 

Appreciate your timely response always. 

Like this?

Client (UIX) to server (VAF or VBScript) communication

Thank you Craig Hawker , your response and the example in the above link does make sense to me.

However, being occupied to another work, I am not able to give it a try this moment. I will check it in practical a bit later. Looking into the example and how both apps are wired-up makes sense to me. I will give it a try and get back to you.  

Thank you once again. 

Hi Craig Hawker , followed the example in provided link UIX to Server but trying multiple tries ending up with the error saying "TypeError: shellFrame.ShellUI.Vault.Async.ExtensionMethodOperations.ExecuteVaultExtensionMethod is not a function"

the below server method is never reached

[VaultExtensionMethod("VaultExtensionMethod_VAF", RequiredVaultAccess = MFVaultAccess.MFVaultAccessNone)]
private string TestVaultExtensionMethod(EventHandlerEnvironment env)
{
SysUtils.ReportInfoToEventLog("Reached to server");
return DateTime.Now.ToLongTimeString()
+ " (the input received from client was: " + env.Input
+ ")";
}

client method i called as per website example

shellFrame.ShellUI.Vault.Async.ExtensionMethodOperations.ExecuteVaultExtensionMethod(
"VaultExtensionMethod_VAF", // The name of the extension method to execute.
"world", // The input (string) to pass it.
function (response) {
// The output (string) will be in response; show it.
MFiles["ShowToast"](response);
});

even i tried 

shellFrame.ShellUI.Vault.ExtensionMethodOperations.ExecuteVaultExtensionMethod(
"VaultExtensionMethod_VAF", // The name of the extension method to execute.
"world")}

Hi Craig Hawker , The difference i see is that example is xsi:noNamespaceSchemaLocation="www.m-files.com/.../appdef-server-v1.xsd" whereas we are using 

xsi:noNamespaceSchemaLocation="www.m-files.com/.../appdef-server-v5.xsd"

Both the applications are explicitly installed, the server and client ones and they are well classified as child under the parent. 

My Server method is as below

[VaultExtensionMethod("VaultExtensionMethod_VAF", RequiredVaultAccess = MFVaultAccess.MFVaultAccessNone)]
private string VaultExtensionMethod(EventHandlerEnvironment env)
{
SysUtils.ReportInfoToEventLog("Reached to server");
return DateTime.Now.ToLongTimeString()
+ " (the input received from client was: " + env.Input
+ ")";
}

My client call is as under

else if (commandId === serverCall) {
console.log("will call the server method now");
shellFrame.ShellUI.Vault.Async.ExtensionMethodOperations.ExecuteVaultExtensionMethod(
"VaultExtensionMethod_VAF", // The name of the extension method to execute.
"world", // The input (string) to pass it.
function (response) {
// The output (string) will be in response; show it.
MFiles["ShowToast"](response);
});
}

 It writes correctly the console log but fails when making call and throws

shellFrame.ShellUI.Vault.Async.ExtensionMethodOperations.ExecuteVaultExtensionMethod is not a function

Difference is only that I am not running/overriding the 

protected override void InitializeApplication(Vault vault)

why i am skipping that is that my application is already installed correctly classified (parent-client) as i explained earlier. 

Would appreciate the earlier response. 

The schema won't matter; keep it as the later one.  Are you using UIXv2 or UIXv1?  This is an older sample for UIXv1 so the specific code shown won't work in UIXv2, but the concept of declaring and calling the vault extension method is identical.  If you do a search on this site you'll be able to find a UIXv2 version.

Thank you Craig Hawker , This is my config in UI application

<application xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xsi:noNamespaceSchemaLocation="">www.m-files.com/.../appdef-client-v5.xsd">

Unfortunately, i could not find a link with example for as you mentioned UIXv2. Could you please help me sharing it. 

Thank you Craig Hawker , This is my config in UI application

<application xmlns:xsi="">www.w3.org/.../XMLSchema-instance" xsi:noNamespaceSchemaLocation="">www.m-files.com/.../appdef-client-v5.xsd">

Unfortunately, i could not find a link with example for as you mentioned UIXv2. Could you please help me sharing it. 

The method you need is this: RunExtensionMethod | M-Files User Interface Extensibility Framework

This is a helper method that I have in a project that shows how it's called:

	async _callVaultExtensionMethod(name: string, input: string):Promise<string|undefined>
	{

		// Run the request.
		const request: RunExtensionMethodRequest = {};
		request.method_name = name;
		request.input = input;
		const response = (await this.Dashboard.ShellFrame?.ShellUI.Vault.VaultExtensionMethodsOperations.RunExtensionMethod(request))?.output;

		return response;
	}

Thanks Craig Hawker , it is helpful.