Hi Nirthika,
Shall we plan to cover section(s) fully with the first version.
Eg: All operations in Human_Resources and Payroll.
Otherwise it'll be difficult to implement a use case.
On Wed, Oct 11, 2017 at 10:13 AM, Nirthika Rajendran
wrote:
> Hi All,
>
> We have planned
Hi All,
We have planned to implement workday connector for EI by referring the
workday API documentation [1] version v29.0.
Workday is a Software-as-a-Service (SaaS) solution developed by Workday
Inc., comprising a set of management applications, covering several areas
like human resources
Hi All,
This issue has been watered-down in v5.2.0 release, now the server starts
successfully. Nonetheless, 'skipping the Startup Order Resolver' has been
identified as a requirement. Created issue [1] to track this feature
request2
[2] https://github.com/wso2/carbon-kernel/issues/1584
Thanks.
If we take other matrices such as CPU, memory etc this service will be too
complicate IMO. That feature is anyway there with JVM matrices in C4
product family. When it comes to C5 based product i think we will still
have some utility for that as well. So we will not need to worry too much
about
> I would suggest the following structure as it would allow users to add any
>> extension for the service discovery.
>>
>> wso2.carbon.serviceDiscovery:
>> enabled: true
>> className : org.wso2.carbon.apimgt.service.discovery.classname
>> cmsSpecificParameters:
>> insidePod:
On Tue, Oct 10, 2017 at 11:22 AM, Pubudu Gunatilaka
wrote:
> Hi Subhashinie,
>
> Please find my comments in line.
>
>
>> This is the deployment yaml configuration that I have added. Note that
>> "insidePod", "caCertLocation", "serviceAccountToken" are just Hashmap keys
>> that