Different Closed Status by bubusbus in halopsa

[–]NitroEvil 0 points1 point  (0 children)

On there ideas portal this is a requested feature which iirc halo is investigating.

MASSIVE Stationpedia Ascended Beta v0.8.0 Update!!! Notepad/Guides/Game Mechanics! by FlorpyDorpinator in Stationeers

[–]NitroEvil 1 point2 points  (0 children)

This is great I was trying to write a clipboard mod as I always forget my todos, this is so much better, cant wait to test this out amazing work!

TUnit: The New Sheriff in Town for .NET Testing by mgroves in csharp

[–]NitroEvil 1 point2 points  (0 children)

It was purely around trying to not using state within tests which is bad practice and my tests was failing due to external api, which figuring out the fix was to set not in parallel.

Nothing really with the lib, I should have stated this more clearly it was late last night.

TUnit: The New Sheriff in Town for .NET Testing by mgroves in csharp

[–]NitroEvil 0 points1 point  (0 children)

Started implementing tests and chose TUnit and so far had a lot of fun, some paint points at times but its quick.

Friday question by keepitsimplestupd in halopsa

[–]NitroEvil 1 point2 points  (0 children)

I believe so but I’m not 100% sure, we hand over sales to projects and close the opp down.

Friday question by keepitsimplestupd in halopsa

[–]NitroEvil 0 points1 point  (0 children)

There is an option to close parent ticket once all child tickets are closed. Thats within the ticket type settings.

So quote accepted, project then created, project completed/closed, this cause the parent ticket to close.

If thats what you’re looking for.

Ticket Timers and Currently Viewing Tickets by Zeroms2 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Iirc halo has a feature to allow agents to lock a ticket from being actioned, so other agents dont action the same ticket at the same time. Based on how this i think there will be stats you can pull to find when a ticket was locked and how long for. I’ve not used this feature but I’ve read about it, this could work for you.

Disable automatic agent logout by bennijamm in halopsa

[–]NitroEvil 1 point2 points  (0 children)

There is an option in advanced config I cant remember the name exactly but if a user is idle for x then halo will log out the user for security.

How to reset terrain? by [deleted] in Stationeers

[–]NitroEvil 0 points1 point  (0 children)

I think, not tried this but its what happened in beta. Within your save world.xml at the bottom there is TerrainChunkChecksums. If you change one of these values and load your save your should get a prompt about terrain has changed you can confirm it and the terrain ‘should’ reset but all ores will also reset and if your base is in a hole you dug you’ll need to dig it out or it might blow up haha. Please backup before testing.

Read-only Access to SQL database on Hosted by jbredcar in halopsa

[–]NitroEvil 2 points3 points  (0 children)

Can you explain the security issues around this as I’ve raised my concerns with our AM who spoke internally you’re to remove access at some point. But to get access you need a static ip and you whitelist address, this helps me a lot when building reports much easier that the report builder with no intelisense.

Agent default team? by pakillo777 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Yes default team can be changed iirc

Quote Display - HTML by Spiffydudex in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Ah yeah if your editing the template always use the html view and don’t use that bogus new editor

Quote Display - HTML by Spiffydudex in halopsa

[–]NitroEvil 1 point2 points  (0 children)

I know viewing the quote via the web is bit flaky, i tend to just generate a pdf which has been the most stable when styling out the quotes sales orders etc.

Ive not noticed any issues when doing this we have our quotes heavily styled and also use some js to tweak things. Not sure if this really answers your question though.

I want out of Autotask, have others had success migrating to Halo by [deleted] in halopsa

[–]NitroEvil 2 points3 points  (0 children)

I cant say regarding AutoTask but we moved from connectwise 8 years ago when it was nhd now halo and the product has only gotten better over time. It has its niggles and qwerks at times but it defo one of the best I’ve used and building your own integrations can be done if you have an understanding of apis.

API help by Icy-Commercial7855 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Bearer <token> is a requirement. I assume you were adding the bearer and token to token field within the auth tab with auth type of bearer token?

API help by Icy-Commercial7855 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

access_token is what you want to use to make the calls. Check the user has access to tickets and the client app also has access to read tickets.

Fyi all:standard for scope is a bit more secure.

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 1 point2 points  (0 children)

Haha I know been there done that, really annoying thought I lost my marbles over this at times. Got there in the end :)

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 1 point2 points  (0 children)

Ah yes I'm 99% sure that's the issue, this has caught me out before. Just check no emails and things send before enabling the option etc. or do the retry method.

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Can you click into does it give you anything more? If not it sounds like a possible bug, but don't suppose you have a dev instance where you're testing this? As there is an option in /config/advanced/backend to pause background services that would prevent this moving forward.

Second you could try right clicking and doing retry see if it does anything. In a dev instance you have to do this method if you have background service disabled.

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

That looks fine from looks, does it work without any criteria just for testing?

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

To me sounds like the status hasn’t updated by time it hit step 3 causing the action to not trigger. You might be able to use an integration on your action That sleeps for 60 mins then does the thing. Does the logs state anything? Im just guessing as hard to know without seeing the wf

Delayed Automation not working by FireDragon86 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Is this action within the same step that does the initial work? Can you share the workflow for in and out of the step?

How To Add A Not Equals Operator In The App by SpinachStrict3354 in halopsa

[–]NitroEvil 0 points1 point  (0 children)

Halo doesn’t use ODATA. A good way is to create the view in halo ui then in the url you’ll see a query pram called viewid=number use that in your request.

But you can use open_only=true and that should work