Pulse issueshttps://support.cubewise.com/code/pulse/-/issues2024-03-26T10:12:51Zhttps://support.cubewise.com/code/pulse/-/issues/4509Credentials not working on Thick client2024-03-26T10:12:51ZMona ChopraCredentials not working on Thick client
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name: Perenti
- OS and Version: [e.g. Windows 2016]
- TM1/PA Version: [e.g. 11.8]
- Pulse Version [e.g. ...
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name: Perenti
- OS and Version: [e.g. Windows 2016]
- TM1/PA Version: [e.g. 11.8]
- Pulse Version [e.g. 6.2.0]: PULSE_SERVER_VERSION=6.3.0
- Browser [e.g. Chrome, Firefox, IE]
- SQL Server Version (if applicable): [SQL 2012]
**2. Items to attached**
- [ ] conf\Pulse.cfg
- [ ] zip the Pulse **logs** folder
- [ ] screenshot of the Status tab in the Pulse About page
- [ ] tm1s.cfg
- [ ] tm1s-log.properties
**3. Describe the bug**
Credentials are not working on Thick Client pulse for Tm1. However, same are working on chrom[Pulse.cfg](/uploads/cffdc3c0a84fc245317cd2d775813f80/Pulse.cfg)
**4. To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**5. Expected behavior**
A clear and concise description of what you expected to happen.
**6. Screenshots**
If applicable, add screenshots to help explain your problem.
**7. Additional context**
Add any other context about the problem here.Shanoo ChauhanShanoo Chauhanhttps://support.cubewise.com/code/pulse/-/issues/4507Search for list of processes ran by a specific user2024-03-25T18:18:20ZCaroline RoySearch for list of processes ran by a specific user**Is your feature request related to a problem? Please describe.**
I am asked what processes were run by a specific user.
**Describe the solution you'd like**
Modify the Query under Chore / Process history to be able to select the use...**Is your feature request related to a problem? Please describe.**
I am asked what processes were run by a specific user.
**Describe the solution you'd like**
Modify the Query under Chore / Process history to be able to select the user instead of the process.
**Describe alternatives you've considered**
Using Chore / Process history but it filters by process.
**Additional context**
noneLuisLuishttps://support.cubewise.com/code/pulse/-/issues/4499ER: add a duration threshold for memory and CPU alerts2024-03-21T02:22:17ZswER: add a duration threshold for memory and CPU alerts**Is your feature request related to a problem? Please describe.**
The CPU alert in its current form is not useful and consequently never used as CPU can spike to 100% (or close to) multiple times per day for all sorts of reasons on a T...**Is your feature request related to a problem? Please describe.**
The CPU alert in its current form is not useful and consequently never used as CPU can spike to 100% (or close to) multiple times per day for all sorts of reasons on a TM1 server that are within normal operating bounds (e.g. loading data with parallel threads, any operation involving MTQ such as query execution or processing feeders). Therefore this alert is never configured as it would lead to multiple false positive reports. What is required to make this alert useful is a _duration threshold seconds_ e.g. set CPU at 99 and duration at 120 seconds would mean the alert will only be triggered if average CPU exceeds 99% for a time window of 120 seconds or longer.
Similarly the Memory alert (while already useful) would be **_much more useful_** if it also had a _duration threshold seconds_ parameter as this would vastly reduce false positive alerts due to memory spiking for short durations. E.g. in some systems memory can spike above 90% for short duration due to processes which are external to TM1 like data loads via tm1py where python uses a lot of memory, or backups where large files are temporarily cached in memory while writing to disk.
**Describe the solution you'd like**
Add configurable duration parameter to BOTH CPU and Memory alert types.
**Additional context**
This would improve monitoring quality by eliminating false positive alerts. The problem with false positives is that they create background noise and increase the risk that legitimate alerts will be ignored or not actioned.6.3.2Elias GonzalezElias Gonzalezhttps://support.cubewise.com/code/pulse/-/issues/4481Regarding Pulse alerts for CPU or memory.2024-03-21T02:21:27Zli FinchRegarding Pulse alerts for CPU or memory.**Is your feature request related to a problem? Please describe.**
We set CPU and memory alerts in Pulse, but sometimes the server's CPU load increases by 90+% in an instant and then drops. At this point, we will receive an email from P...**Is your feature request related to a problem? Please describe.**
We set CPU and memory alerts in Pulse, but sometimes the server's CPU load increases by 90+% in an instant and then drops. At this point, we will receive an email from Pulse, warning that the CPU usage is 90+% and has exceeded the threshold of 90+%. This requires us to frequently check the server, but in reality, the server is functioning normally.
**Describe the solution you'd like**
I hope that Pulse's alert setting has a feature that can monitor CPU or memory usage when it exceeds a threshold and lasts for a period of time(Customizable), and then Pulse sends out the alert email. We don't want Pulse to send emails every time the threshold is triggered, as this can cause us to receive a lot of alerts and overlook the truly problematic emails.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.6.3.2Shanoo ChauhanShanoo Chauhanhttps://support.cubewise.com/code/pulse/-/issues/4458No TM1 Servers Connect2024-02-22T11:36:19ZAlex MarshNo TM1 Servers Connect![image](/uploads/61291073e105ab3181be463a103ae10e/image.png)
we are seeing this all of a sudden when logging in to Pulse. if you send me a link I can upload the Pulse Log![image](/uploads/61291073e105ab3181be463a103ae10e/image.png)
we are seeing this all of a sudden when logging in to Pulse. if you send me a link I can upload the Pulse Loghttps://support.cubewise.com/code/pulse/-/issues/4457Removal of Existing Objects with Migration Package (CleanUp of Legacy/Existing)2024-02-22T05:56:01ZDonovan AustinRemoval of Existing Objects with Migration Package (CleanUp of Legacy/Existing)**Is your feature request related to a problem? Please describe.**
We have situations where we update/enhance modules within TM1.
In this process, we sometimes have to Split current existing Processess into more than one process.
This ...**Is your feature request related to a problem? Please describe.**
We have situations where we update/enhance modules within TM1.
In this process, we sometimes have to Split current existing Processess into more than one process.
This results in the process name changing to align with each of their actions, however as Pulse only 'creates' objects, we sit with a situation where we have old processess/dimensions etc staying in our PRD Instance thats not needed.
If possible, can there be means, via the deployment package to REMOVE certain objects in the target instance with the deployment?
**Describe the solution you'd like**
Have the Migration Package have two primary tasks:
Migration Objects - existing.
Remove Objects - New (Remove from Target Instance to avoid sitting with unused/legacy objects that have been replaced)
**Describe alternatives you've considered**
Deploy cleanup process with the migration package to remove objects via CommandPompt etc as we don't have Admin nor Access to DB.
However, then we sit with the Cleanup processes in PRD. Last option would be to go create a primary cleanup process with multiple parameters and run that individually for all objects to be deleted post deployment.https://support.cubewise.com/code/pulse/-/issues/4449Pulse does not compact elastic directory after threshold exceeded but continu...2024-03-11T10:11:23ZswPulse does not compact elastic directory after threshold exceeded but continues to send alerts
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- OS and Version: Windows Server 2016
- TM1/PA Version: 11.8
- Pulse Version 6.3.1
**2. Items to attached**
- [X] conf\Pulse...
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- OS and Version: Windows Server 2016
- TM1/PA Version: 11.8
- Pulse Version 6.3.1
**2. Items to attached**
- [X] conf\Pulse.cfg
- [X] zip the Pulse **logs** folder
- [X] screenshot of the Status tab in the Pulse About page
- [ ] tm1s.cfg
- [ ] tm1s-log.properties
[Pulse.cfg](/uploads/7d180f4ddca56754ba8ce10269d69f4b/Pulse.cfg)
[logs.7z](/uploads/17cd2958c7065b147c0606c7599ae56b/logs.7z)
![image](/uploads/3abc02be26bb18c3bd303cb24cfdeae3/image.png)
**3. Describe the bug**
Maximum size for elastic search directory has been configured at 50GB. When this limit is exceeded Pulse sends error alerts **and should also automatically compact the directory by removing older files.** However, we have bee receiving alerts for several days and the elastic directory continues to grow and Pulse has not deleted any files.
**5. Expected behavior**
Pulse should automatically compact the directory and not continue to send alerts.
**6. Screenshots**
![image](/uploads/7f0ee73ec38f67e57e449253a9b08105/image.png)Johnson AbrahamJohnson Abrahamhttps://support.cubewise.com/code/pulse/-/issues/4436Issue in installing the PostgreSQL ODBC Driver2024-02-16T11:01:23ZJeffry LiandoIssue in installing the PostgreSQL ODBC DriverHi Cubewise
I'm trying to install to get the Pulse db via PostgreSQL as in instructed in here https://code.cubewise.com/docs/connecting-to-the-pulse-databases-through-an-odbc-driver but getting an error. Would you please advise me as I ...Hi Cubewise
I'm trying to install to get the Pulse db via PostgreSQL as in instructed in here https://code.cubewise.com/docs/connecting-to-the-pulse-databases-through-an-odbc-driver but getting an error. Would you please advise me as I may have missed something?
![image](/uploads/9dd4725bb94c91492da8e1b0262eb374/image.png)Erik CarmonaErik Carmonahttps://support.cubewise.com/code/pulse/-/issues/4416Trace commits back to migration package2024-02-09T05:06:45ZgngTrace commits back to migration package**Is your feature request related to a problem? Please describe.**
(Posted the question on the Cubewise Forum. But didn't get a reply yet so raising this here)
https://forum.cubewise.com/t/audit-trace-commits-back-to-migration-package/6...**Is your feature request related to a problem? Please describe.**
(Posted the question on the Cubewise Forum. But didn't get a reply yet so raising this here)
https://forum.cubewise.com/t/audit-trace-commits-back-to-migration-package/6180
A client using Pulse needs to provide proof to IT audit on the changes made in production.
The idea is to look at an object changed, find out the deployment package used, and see all the related objects modified for the change request.
The manual description on the migration package will also reference the Change Request ID related for this deployment
allowing them to reference all associated documentation from: requirements, test results, sign-off, and post implementation verification.
**Describe the solution you'd like**
Can a migration package also display the commits of each modified object to allow easy navigation to it to view the code difference.
Vice versa, looking at an object commit, can there be a link that navigates to the migration package used to deploy.
Currently the user has to associate the commits and migration package manually.
(/uploads/8f4dd8e3a32e30946497623d43fde8f8/Commit_and_Migration.png)https://support.cubewise.com/code/pulse/-/issues/4405ElasticSearch and PowerBI - ODBC questions2024-02-14T13:58:57ZAlexis BonnetElasticSearch and PowerBI - ODBC questionsHi CODE team,
A Pulse client wishes to analyze its Pulse data with PowerBI instead of Kibana.
A bit of research led me to believe it's possible:
1. https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-client-apps-powe...Hi CODE team,
A Pulse client wishes to analyze its Pulse data with PowerBI instead of Kibana.
A bit of research led me to believe it's possible:
1. https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-client-apps-powerbi.html
2. https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-odbc-setup.html#dsn-configuration
I'm running Pulse locally and I installed the ODBC client (https://www.elastic.co/downloads/past-releases/odbc-client-7-0-1), used the same port 8097 at Pulse ES but I'm running into some issues. I'm not able to get past this:
![image](/uploads/ce16ee545c6cece963637a4ea7b544a0/image.png).
![image](/uploads/91d653a01e947e56dfe572218f69bf20/image.png)
The latest ODBC driver version is not compatible so I'm stuck with this 7.0.1 version which is different from the config guide above (less parameters to configure).
I'm also wondering if we are not limited by licensing? https://discuss.elastic.co/t/is-specific-license-required-to-use-elastic-search-odbc-driver/286089
That's why I'm reaching out to any ES expert of the CODE team to see if this is possible! Vincent suggested me otherwise to look at a PowerConnect option which could be a good workaround.
Thanks in advance for your help!
AlexisLuisLuishttps://support.cubewise.com/code/pulse/-/issues/4403Pulse - Full Package Roll Back (vs Object by Object)2024-02-05T05:52:02ZDonovan AustinPulse - Full Package Roll Back (vs Object by Object)**Is your feature request related to a problem? Please describe.**
Not a problem, but a Feature request.
We Promoted a Package to our PRD Env, however through our test case and UAT Sign off, a specific scenario was missed causing the p...**Is your feature request related to a problem? Please describe.**
Not a problem, but a Feature request.
We Promoted a Package to our PRD Env, however through our test case and UAT Sign off, a specific scenario was missed causing the promoted module to give issues.
We then had to Roll-Back these items as it impacted a core function but discovered that one can't roll back a **Package as a whole**. We had to roll back Object by Object which caused more interim issues (This is time consuming sometimes causing the problem to get worst before it gets better and we weren't able to notify an outage.
**Describe the solution you'd like**
In a Package View, have the option to Roll Back the full Package with all their objects.
My assumption would be that the existing object version/timestamp etc is stored when upgrading and those objects can just be re-migrated back into the system upon rollback.
**Describe alternatives you've considered**
We started a backup of the PRD Instance, created a Package from the backup instance and promoted those objects back to Live PRD (As a rollback).https://support.cubewise.com/code/pulse/-/issues/4400Can't see who approved a package (Can only see the Notification group)2024-02-07T02:05:45ZDonovan AustinCan't see who approved a package (Can only see the Notification group)
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3.1
- Browser Chrome with ad Login
Firstly, we appreciate the Approval Function ...
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3.1
- Browser Chrome with ad Login
Firstly, we appreciate the Approval Function in Pulse, but we require some items to ensure it covers all the required SOX Controls.
1 - When a Package Approval is requested, one indicates a Notification Group who receives an email. (**This is perfect**)
2 - When a person, with Approval Rights (Per security Group) approves a Package that allows the execution of the Package. **Thats perfect** except for enhancement request #4399
_Here's where the problem with the Auditors start._
3 - On the Approval Page, one can't see **WHO** actually approved the request. How can one identify who actually approved the migration.
4 - In the actual Migration Package, it indicates in the 'Approval History' that the item was approved, but again one can't see **WHO** actually approved the package. It only provides a Notification Group who can exist out of more than one person.
5 - The Auditors then asked who's in our Approval Notification group as that should pinpoint who would have possibly approved it, but then they identified that the list in that group can be changed on demand without history/last modified. So in a Year that group might change and one won't have record who approved the item.
**Proposals/Solution**
1 - Approval Requests tab, add a column indicating the **individuals name** who approved the Package. (The 'Submitted To' does not provide the required clarity as that can change over time).
2 - In the 'Migration Package' page, in the 'Approval History' tab, indicate the individuals name who approved the Package. (The 'Submitted To' does not provide the required clarity as that can change over time).
3 - The Execution History page, add a column stating the individuals name who approved the package (Similar to Created By/Executed by).
**Impact:**
_We can't upgrade to the newer version due to the Auditors not satisfied with the Evidence/Ownership of the Approved By item, there's no link to a individual when a Package has been approved. _https://support.cubewise.com/code/pulse/-/issues/4399Pulse 6.3.1 - Approval Workflow (Creator can Deploy Package)2024-02-07T09:39:56ZDonovan AustinPulse 6.3.1 - Approval Workflow (Creator can Deploy Package)**Is your feature request related to a problem? Please describe.**
For SOX, we can't have the Creator of a Migration Package Deploy their own Package (**Even if approved**).
Currently, once a Package is approved, the creator can deploy ...**Is your feature request related to a problem? Please describe.**
For SOX, we can't have the Creator of a Migration Package Deploy their own Package (**Even if approved**).
Currently, once a Package is approved, the creator can deploy the Package.
**Describe the solution you'd like**
Person A - A TM1 Developer and developed a solution to be promoted to PRD.
Person B - A TM1 Developer (Not Person A)
Person C - System Owner/Team Lead/Product Owner (Part of Notification group: Control Owner)
Person A:
Can create Package with ID #00001
Can request approval to Notification Group: Control owner.
Can't approve based on Security Group
**CAN't deploy Package ID #00001 (Whether the Package #00001 is approved or not approved. Author can't deploy their own Package)**
Person B:
Can't approve based on Security Group
Can't deploy package if not Approved.
Once Package ID #00001 is Approved, they can Execute/Deploy Package ID #00001 BECAUSE THEY AREN't the Auther of the Package.
Person C:
Can't create a Package with group Security
Can Approve a Package as they have 'Approve Package' security.
**Describe alternatives you've considered**
Nonavailable, except manual controls.
**Additional context**
Add a config where a creator/author can't deploy a package where they are the creator/author.https://support.cubewise.com/code/pulse/-/issues/4398Pulse 6.3.1 - Rejected Migration Packages should be locked/non-deletable2024-02-01T07:48:07ZDonovan AustinPulse 6.3.1 - Rejected Migration Packages should be locked/non-deletable**Is your feature request related to a problem? Please describe.**
When a Migration Package is REJECTED via the Approval Function, the Package should be Locked (i.e. one should not be able to delete a package once rejected). This is sim...**Is your feature request related to a problem? Please describe.**
When a Migration Package is REJECTED via the Approval Function, the Package should be Locked (i.e. one should not be able to delete a package once rejected). This is similar to a Migration package that has been executed in that one can't then go and delete the Package.
The Auditors always state, that if something is rejected, its not a 'bad' thing, its showing that the process/control works.
**Describe the solution you'd like**
Once a Package is Rejected, the Package should be locked and one should **NOT** be able to delete/change/recreate the Package.
**Describe alternatives you've considered**
We ensure we don't delete a Rejected Package, however the Auditors requires a system based control.https://support.cubewise.com/code/pulse/-/issues/4397Pulse 6.3.1 - Approval Request doesn't clear if a Migration Package is Deleted2024-03-05T01:48:11ZDonovan AustinPulse 6.3.1 - Approval Request doesn't clear if a Migration Package is Deleted
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3...
> Mark the issue as **Confidential** to keep log files and screenshots private
**1. Key information:**
- Company / Customer Name: Digital Outsource Services
- OS and Version: Windows 2016
- TM1/PA Version: N/A
- Pulse Version 6.3.1
- Browser Chrome with AD Login
- SQL Server Version (if applicable): N/A
Issue Statement:
Create a Migration package.
Request a relevant Approval.
Approval Request gets created in the 'Approval Requests' tab.
Its identified that the Packages should be deleted due to xyz reason.
We delete the Migration Package PRE-APPROVAl/Execution
**ISSUE:** The Approval Request still exists/stays in the 'Approval Requests' tab.
Expectation:
1 - If a Migration Package is Deleted PRE-APPROVAL & Execution, the Approval Request should also disappear/get removed.
2 - If a Migration Package is REJECTED, then the Packages should be locked, and one can't delete/execute that package (as if its been deployed). This is just a SOX Control as a Reject isn't a 'bad' thing, its showing the control works.6.3.2Elias GonzalezElias Gonzalezhttps://support.cubewise.com/code/pulse/-/issues/4387Offline Migration: Creation from source control fails after deletion of tm1 o...2024-01-29T03:24:52ZJohnson AbrahamOffline Migration: Creation from source control fails after deletion of tm1 objects in source service.This issue occurs only when trying to create a offline package from source control after deleting a tm1 object (dimension/ cube) in ARC/TM1 Architect.
1\. Create dimension dimA, dimB in a source tm1 server in ARC.\
2. Run update docume...This issue occurs only when trying to create a offline package from source control after deleting a tm1 object (dimension/ cube) in ARC/TM1 Architect.
1\. Create dimension dimA, dimB in a source tm1 server in ARC.\
2. Run update documenter in pulse.\
3. Create a offline package from source control, able to create one.\
4. Delete dimA and run update documenter.\
5. Create an offline package using source control option.\
6. When saving the package you get following error
![dimA_offline_migration_issue.png](/uploads/9f10c1eb84004fe5a18b4b7348cab0e6/dimA_offline_migration_issue.png)
An error is thrown when a cube is deleted and an offline package is created from source control after that.
![cubeA_offline_migration_issue.png](/uploads/3557258d2f15f28948c02cc269bd94dc/cubeA_offline_migration_issue.png)
Expected behaviour, shoud be able to create the offline package. (Sliently catch the exception and log it.)Johnson AbrahamJohnson Abrahamhttps://support.cubewise.com/code/pulse/-/issues/4380Flow Diagrams doesn't include Control Objects2024-01-19T06:20:44ZRupesh KumarFlow Diagrams doesn't include Control ObjectsHi Team - Please confirm if there is an option to include control objects (Element Attribute cubes etc.)while generating flow diagrams, a number of our rules refer element attribute cubes and we would like them to show up in the flow dia...Hi Team - Please confirm if there is an option to include control objects (Element Attribute cubes etc.)while generating flow diagrams, a number of our rules refer element attribute cubes and we would like them to show up in the flow diagram however don't see any option available, refer attached screen-print![Flow_Diagram_Issue](/uploads/29be25a0622e58d9f803be4b961187ee/Flow_Diagram_Issue.png)
Version: 6.2.0https://support.cubewise.com/code/pulse/-/issues/4372Error while importing package2024-02-09T10:22:13Zpayal dosarError while importing packageHi Team,
We are getting error while importing package in TM1pulse.
This is an urgent request and hence will require assistance.
We are attaching relevant logs for the same, happy to get into a call for quick resolution.
[pulse.zip](/...Hi Team,
We are getting error while importing package in TM1pulse.
This is an urgent request and hence will require assistance.
We are attaching relevant logs for the same, happy to get into a call for quick resolution.
[pulse.zip](/uploads/c9c702d2fef866b1641975b3ce84492b/pulse.zip)
Thanks,
PayalElias GonzalezElias Gonzalezhttps://support.cubewise.com/code/pulse/-/issues/4364Power BI threads causing server crash in IBM PA2024-01-02T14:10:08ZGaurav JadhavPower BI threads causing server crash in IBM PAHi team,
I am working with Huntsman, and we are using Cubewise tools like ARC, Pulse and Connector for Power BI.
In previous month we faced an issue where a user was trying to open a view in Power BI using mdx query generated in IBM PA...Hi team,
I am working with Huntsman, and we are using Cubewise tools like ARC, Pulse and Connector for Power BI.
In previous month we faced an issue where a user was trying to open a view in Power BI using mdx query generated in IBM PA cube view.
He unintentionally opened 17 such instances and these threads were running in IBM PA even after user disconnected the session in Power BI. This caused threads to go into wait mode (including security refresh and save data) and server was in unresponsive state. The only option left was to restart the IBM PA instance. Due to this issue the server was not available for 600 minutes and there were some cubes where user reported data loss.
Can your team please check what caused issue with Cubewise connector for Power BI ?
We have already raised this issue with Cubewise consultant Guido Tejeda gtejeda@cubewise.com, Logging an official ticket.Elias GonzalezElias Gonzalezhttps://support.cubewise.com/code/pulse/-/issues/4362The URL of Arc that will aid in further updates of TM1 Servers. Default: http...2023-12-26T15:50:02ZJanardhan GaddamThe URL of Arc that will aid in further updates of TM1 Servers. Default: http://[ServerName]:7070Hi Team,
we are not able to access the default url for Arc. Our current version is 6.3.0. Please suggest for the same.
Regards,
Janardhan G
![image](/uploads/95b41003b7f26c3fd00e36a4ee96d087/image.png)Hi Team,
we are not able to access the default url for Arc. Our current version is 6.3.0. Please suggest for the same.
Regards,
Janardhan G
![image](/uploads/95b41003b7f26c3fd00e36a4ee96d087/image.png)